I just rooted my HOX+ and installed CWM and flashed 23/06 Carbon nightly on it. For a couple of days everything was fine
until today when it said "Unfortunately.. blah blah.. systemui has stopped working". Every time I boot up the phone it gives me
this message and I can't do anything. Rebooting doesn't help, I tried wiping everything and reflashing, still nothing. I did some
research and found a thread about face unlock might causing this. I disabled the face unlock but didn't work. I don't know if it's
caused by some google app cuz when I reflashed everything, including gapps, first there was no problem, but I think when it was
installing google search the error message came again. Have anyone else experienced this error? Any solutions?
AveEagle said:
I just rooted my HOX+ and installed CWM and flashed 23/06 Carbon nightly on it. For a couple of days everything was fine
until today when it said "Unfortunately.. blah blah.. systemui has stopped working". Every time I boot up the phone it gives me
this message and I can't do anything. Rebooting doesn't help, I tried wiping everything and reflashing, still nothing. I did some
research and found a thread about face unlock might causing this. I disabled the face unlock but didn't work. I don't know if it's
caused by some google app cuz when I reflashed everything, including gapps, first there was no problem, but I think when it was
installing google search the error message came again. Have anyone else experienced this error? Any solutions?
Click to expand...
Click to collapse
Same here. It started yesterday. Tried to flash older and newer ones with full wipe including cache and dalvik cache, but it still does not help.
I flashed a sense rom (ARHD) and wiped nearly everything on the phone before I installed the new rom. I did multiple factory resets, multiple dalvik wipes, multiple cache wipes and I formatted the whole system a few times (=format system). Afterwards I flashed ARHD and my phone works brilliant now. Try this I hope it works on your devices!
I made a fresh install of Carbon on my HOX+ last week (CARBON-KK-NIGHTLY-20140802-1713-enrc2b, fwiw), and it worked just fine up until last night when I encountered this exact problem. The official enrc2b Carbon thread contains a post that would seem to indicate that the problem is with Google Plus (though there isn't much in the way of evidence).
In any case, completely wiping and re-installing the phone appears to be a solution, but I would submit that it's temporary - if the problem is some sort of incompatibility with one or more Google Apps, then the issue will simply return at some point.
Hopefully the root cause will be determined and a fix will be forthcoming. Until then, I suspect we're all just sitting on time-bombs.
i think the problem comes really from the google+ app.
i did a clean install after the crash with the small pa gapps, wich didn't contains the google+ app.
Then i reinstall al my apps one by one except g+ and now everything works perfect again.
It's a little bit more work, but the only way i know to fix..
Hope it helps
I had the same problem with Carbon. I've installed Carbon a view days ago (comming from Mokee) and after the latest G+ Update my SystemUI stopped. A dirty flash didn't solve the problem.
So I restored my Mokee Backup and here everythink is great (with the latest G+ update)
Related
I have my phone rooted and installed the FTS V2.4 ROM onto my phone, followed the install instructions. On startup I get a force close error, The application Motorola services (process.com.motorola.service.) has stopped unexpectedly. Please try again. I then get the process com.motorola.home.other has stopped. Everything else works fine. I do get another error when trying to place an email and date & time widget. Is there a fix for this? It doesn't stop the phone from functioning just would like to fix it.
That is usually caused by a bad flash or incomplete wipe. Go back into the recovery wipe everything a couple of times reflash the rom and that should take care of it. I have had that happen on multiple phones with multiple roms.
arsmithsr said:
That is usually caused by a bad flash or incomplete wipe. Go back into the recovery wipe everything a couple of times reflash the rom and that should take care of it. I have had that happen on multiple phones with multiple roms.
Click to expand...
Click to collapse
So after booting into recovery I do wipe data/factory reset a couple times? Anything else I should wipe a couple times? And then do install zip from sdcard? Also, my friend said after it installs I should leave it for 10-20 minutes, is this true?
you can manually wipe the cache and dalvic cache 2 or 3 times each then factory reset a couple times then flash your rom again. What has happened is you have ssome files from the old rom and some files from the ne rom this causes the issues you are seeing. You could probably just factory reset a couple of times Cauculin? has made a special wipe becuase of these issues sometimes it doesn't format right that's why you need to do the multiple wipes to be sure it took.
Similar problem on virgin Razr
I get this each time I reboot " process com.motorola.home.other has stopped unexpectedly, Please try again. Force close. FC is my only option.
It has appeared a few other times but with no regularity. Like the OP I still have full function and use but I'm sure it is a sign of possibly other problems brewing.
From what I have read it looks as if a complete reset might be the only cure but I'm hoping to find another solution.
Q: Is "com.motorola.home.other" actually a file, or does it refer to a file that could possibly be copied back over from a backup if it is corrupt.
While writing this post this problem occurred again after closing an app, which has me even more concerned.
Many thanks
X/BillyD..
im on stock dxlp7 via kies. last time it was working was when i switch on the wifi and got stuck (known issue). because i can't wait, i rebooted it by holding the power button and use feature there.
during boot-up, i saw the upgrading OS as if it was a new upgrade to 4.0.3. then there all apps started to force close. only few apps work and mostly are those that come preinstalled.
im doing backup as of this writing and saw one thread that wiping the cache fixes it. i hope wiping the cache really fixes this. created thread because the other was was on 2.3.x. this one is on ICS.
what went wrong with my phone? is this a known issue? i can't find that much info on this.
Do a factory reset.
i first tried to wipe the cache. didn't work.
i did factory reset so far its working fine. no other apps yet except preinstalled.
what went wrong there?
Honestly, that's really hard to say. Something has obviously corrupted some system apps/files by the sound of what you're describing.
Important thing is you seem to have fixed it. See how you go as you start reinstalling your apps.
Flash05 said:
i first tried to wipe the cache. didn't work.
i did factory reset so far its working fine. no other apps yet except preinstalled.
what went wrong there?
Click to expand...
Click to collapse
so far nothing weird happening. installing the apps is ok. configuring one by one sucks.
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?
So I have had some weird issues. I was running on Slimbean when this started. Out of nowhere my device started freezing from time to times, like if I was writing a text message or something. Everything would just stop and then I had to reboot the system to get it functional again. This started to get annoying so I did a clean reinstall of Slimbean, formatted system and cache etc. That didn't help so I decided to change the rom. I installed another AOSP rom, Carbonrom but that did't help (of course I did a clean install). After that I decided to try if changing the rom to Sammy based would help. I was wrong.
At this point I taught that something with my hardware would be broken. So I installed triangleaway, formatted system and then installed samsung's official firmware with odin. Then I did a factory reset from system settings. My plans were to send the phone to warranty but strangely after running the stock rom for about a week, the freezing problems were gone, when earlier it was a daily thing.
So now I'm wondering what could have it been and why? If I reroot and install a custom rom now, will the freezing start again?
Hi there,
There's a big thread on this, with a solution(I can confirm that it worked for me):
http://forum.xda-developers.com/showthread.php?t=2133401
GL
eytan123 said:
Hi there,
There's a big thread on this, with a solution(I can confirm that it worked for me):
http://forum.xda-developers.com/showthread.php?t=2133401
GL
Click to expand...
Click to collapse
Oops sorry I used search but somehow missed that thread
that's cool, for the next time.
hope you'll end this cause it really is very annoying
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.