i have galaxy s it's work normally and it's have cm 10
but today when i turn on give me this note
(Unfortunately, the process com.google.process.gapps has stopped)
another note after i make it's ok
(Unfortunately, setup Wizard has stopped)
and i press ok again
give me firs one and still like that give me this two note again again again ...........
because that i can't work in my tell phone
i try install cm10 again and gapps but nothing
and wipe data/factory reset
but it's not work
i need to fix it today i can't live without my phone
CM10 is still in nightlies right?
meaning that they are a bit unstable and not really that useful as a daily ROM if you don't like the kind of surprises you have described.
find another ROM or revert to a stable build of CM10
Related
Hello all,
I have ICS (4.0.3 XXLPH kernel and modem), resurrection ROM 9.3 on my SGSII, when every I try to dial any number directly it hangs, and I need to press home button, and the dialer kept hanged, I tried to resinstall the ROM again and again, full wipe of course, clear cache clear dalvic and fix permissions, this happens to me since ICS resurrection 9.1, I beleive there is something wrong with me only cause no one adviced about this in the ROM section.
if you have any idea or any experience you may share, please do it and I will apprecite it
note: I can not dial any number at all since 1 month , I can only call the numbers I have them saved. the problem solved when I rstart the phone for sometime only, thne back to be slow, then complete stuck
alot of thx
Bye
Salloum
just want to draw your attention, that after hangs, a massive battery drain happens to my phone, and I can feel the heat around the back camera.
As the rom is built on a leaked buggy beta test rom ICS expect problems that's what beta means .
Problem unlikely to be the phone and it now has no warranty .
jje
even it only happens to me... but it's right what u said, this is what beta is made for ... alot of thanx for your reply , I will try to install another ROM soon
This is happening on my phone too! strange! have you found the culprit of the issue? Can share with me?
ahm_salloum said:
Hello all,
I have ICS (4.0.3 XXLPH kernel and modem), resurrection ROM 9.3 on my SGSII, when every I try to dial any number directly it hangs, and I need to press home button, and the dialer kept hanged, I tried to resinstall the ROM again and again, full wipe of course, clear cache clear dalvic and fix permissions, this happens to me since ICS resurrection 9.1, I beleive there is something wrong with me only cause no one adviced about this in the ROM section.
if you have any idea or any experience you may share, please do it and I will apprecite it
note: I can not dial any number at all since 1 month , I can only call the numbers I have them saved. the problem solved when I rstart the phone for sometime only, thne back to be slow, then complete stuck
alot of thx
Bye
Salloum
Click to expand...
Click to collapse
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
theking1st said:
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
Click to expand...
Click to collapse
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
cars1189 said:
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
Click to expand...
Click to collapse
Thank you @cars1189 for your answer. I used the device thread to do it but the problem is, I let it spinning for more than 5 hours. I have flashed many roms in my phone since i had it (more than 10 times or more) and i know that it does not take more than 10 mins max to install. But don't worry after that i went back and restored my previous CM 9 rom and right now i'm on the CM 11 build of 1-29-14 of your CM mass thread. It works fine, not at 100% but it doesn't drain my battery like your CM 10.2 build of 1-11-14 and it is almost stable. I will try tonight to use your ADC kernel with the jfbs CM 11 rom that first didn't work for me because I saw in your thread that this kernel may help it to load and install without the spinning issue. So i will give it a shoot. But anyways thanks for your answer and it means a lot to me really. :good:
GOOD
@cars1189 , I'm actually running the 6-18-14 build of CM11 and as far as it goes, i'm not encountering any major issue at the moment. The theme engine is working fine for me and battery life is great for my usage. I use this build as a daily driver, and it does a great job. Calls, texts, data, wifi, Bluetooth and GPS are all working. I had issues before with the amount of RAM available, but now that it has 375MB of RAM, it is more snappy. Just :good: Thank you for your work on our to make our phone still valuable today!! THANKS MAN!!!!!!
Hello..
I have a strange problem with my Galaxy ace s5830i mobile...
it was on same rom that were from start, and then i decieded to switch to another one.
First option was Miui, and after that switched to cm7 totoro rc c4 (full name of it , writing it cos i am not sure how to explain it on the other way )
but problem is, after every restart, my mobile loose everything that is done on it, and do something like factory reset...
for example, it will bring back original theme, forgot wifi password, and everything else...
also, cannot install gapps ( actually, i can, but after restart they gone)
anyone have solution for this one problem?
Wipe data once from recovery
Had some sort of same problem, that fixed it.
Gesendet von meinem Nexus 5
johndcrambo said:
Hello..
I have a strange problem with my Galaxy ace s5830i mobile...
it was on same rom that were from start, and then i decieded to switch to another one.
First option was Miui, and after that switched to cm7 totoro rc c4 (full name of it , writing it cos i am not sure how to explain it on the other way )
but problem is, after every restart, my mobile loose everything that is done on it, and do something like factory reset...
for example, it will bring back original theme, forgot wifi password, and everything else...
also, cannot install gapps ( actually, i can, but after restart they gone)
anyone have solution for this one problem?
Click to expand...
Click to collapse
Why did you flash cm7 totoro? Galaxy ace i is not totoro. It is cooperve.
johndcrambo said:
Hello..
I have a strange problem with my Galaxy ace s5830i mobile...
it was on same rom that were from start, and then i decieded to switch to another one.
First option was Miui, and after that switched to cm7 totoro rc c4 (full name of it , writing it cos i am not sure how to explain it on the other way )
but problem is, after every restart, my mobile loose everything that is done on it, and do something like factory reset...
for example, it will bring back original theme, forgot wifi password, and everything else...
also, cannot install gapps ( actually, i can, but after restart they gone)
anyone have solution for this one problem?
Click to expand...
Click to collapse
I kinda faced the same problem twice, check if you have internal memory, if it says 0.0bytes, then I know how to fix it
Hello there!
Recently I had some problems with random rebooting my device, so I decided to wipe the entire phone and install new version of CM12.1. I hadn't any problems during that process. I installed my favourite apps and configured my device. Everything worked quite nice and fast. First problem appeared when I did first reboot. Phone just.. gets bootloop. No matter what i'm doing - next reboot is always bootloop. I don't have idea what should I do CM11 starts to annoy me a bit.. I'm using a Huawei Ascend G620s-L01.
Any kind of help would be much appreciated!
Regards, Mat. @edit
Oh.. Same thing happens on CM13..
Anybody has an idea? :/ I realised that the AOSP ROMs based on Lollipop works! But after first reboot SIM stops working.. I'm gonna die..
edit:
ah, I noticed that radio and sim card stopped working on almost every ROM. It works only on some CM roms..
Hello,
First, I want to say that I hope this is in the right subforum. Otherwise, please, move this thread.
So I have a big issue with using Cyanogenmod 12 and 13 on two totally different devices; the international version of Samsung's Galaxy S4, and the OnePlus One. Installing either version of Cyanogenmod works perfect, but as soon as OpenGApps is flashed (Tried nano, pico...) and Android is loaded up, it gets stuck in an infinite stream of crash messages, telling me that "Unfortunately, the process com.google.process.gapps has stopped."
I have found a fix. BUT this only works on CM13. If you click-spam your way through the first time launcher, then navigate to Settings and find System Restore and perform said operation, then the crashes with magically go away and the phone will run without any problems at all. This is good enough for my OnePlus One.
However: There is no stable build of CM13 for the Galaxy S4 international, in the latest Nightly-build I tried for it, call audio was not working at all.
Does anyone know why this is happening, and how do I go about fixing this, other than the solution I found above?
Help is much appreciated!
I really suspect it being an OpenGApps issue. Though I do not understand why as the same build/phone has worked fine with it before.
Are there any reliable alternatives?