Hello,
I'm currently running Xylon - May 15th build and Franco Kernel 137 and May 15 Banks GAAPS.
I cannot receive phone calls, as soon as the phone starts to ring I get com.android.phone has stopped notice.
I can make calls but the com.android.phone service stops immediately after I hang up.
I tried changing Kernels from Franco M2 to 134 to 135, 136 and 137 but the issue persists
I updated from May 9th Xylon to May 15th and no dice still.
Wipe Dalvik/Cahe and all that stuff.
Changed GAAPS versions.
Nothing seems to fix it. Can anyone point me in the right direction?
All better
Nevermind folks.
I fixed it by doing a factory reset (boo!) , reinstalling newest Zylon, Flashing Newest Official GAAPS and reinstalling newest Franco.
Not the route I wanted to go but if it works, it works.
Related
Mysterious AOKP 4.2.2 rom, Feb 22 build, faux 123 kernel, .33 radio, twrp. Took a pic, decided to take another one, hit the shutter, the phone froze, and then rebooted. downloaded some apps from the play store, rebooted on its own.
I haven't had any problems with stock 4.2.1 before, but then I wasn't really using the phone before and tinkering with it. Don't know if it was related to a wrong version of gapps or a dirty rom install or worst case scenario-hardware problems?
I followed the guide here. under TWRP there was an option to Format everything which i haven't tried.
http://www.android.gs/install-paranoid-android-4-2-1-custom-rom-for-google-nexus-4-e960/
gapps 4.2.2
http://donandroid.com/gapps
I also noticed it came with some apps called Android tweaker free and Battery Guru. Could that be cause of it? Compatiblity issues? Should I go back to stock 4.2.1 or try a different rom?
I have built BeanStalk (cm10.1 based) using the latest jflteatt files (breakfast jflteatt) twice now and have received the same message.
The phone is able to boot, but the first thing that pops up is an alert saying the process com.android.phone has stopped.
I have done complete wipes and the message still appears.
I was able to build BeanStalk on 5/31 and everything worked fine, but I was hoping to get the latest cm10.1 adjustments, like the BT fix, in the build.
chrisc93 said:
I have built BeanStalk (cm10.1 based) using the latest jflteatt files (breakfast jflteatt) twice now and have received the same message.
The phone is able to boot, but the first thing that pops up is an alert saying the process com.android.phone has stopped.
I have done complete wipes and the message still appears.
I was able to build BeanStalk on 5/31 and everything worked fine, but I was hoping to get the latest cm10.1 adjustments, like the BT fix, in the build.
Click to expand...
Click to collapse
the forum title clearly states developer only
Hopefully you posting here was a mistake
Thread moved to AT&T S4 Q&A.
Hi guys,
Im currently running CM 10.1-2013072 Nightly and any time I try to update via OTA my tablet starts freaking out. all the latest versions are 10.2. The Stock keyboard repeatedly force closes. Apps that were installed prior to the update are no longer installed. I have tried doing a full wipe (factory, cache, system) then install the latest nightly. It installs fine but when It loads up to the initial configuration screen the stock keyboard repeatedly ForceCloses still and I cant do anything with the tablet. I have gapps-20130301.....is there a newer one or is this still the latest gapps? Thanks!
UPDATE: I was using the wrong gapps version. All is good now
Hello there.
I recently tried to install the most recent version of PAC ROM for my Galaxy S4 (Sprint, SPH-L720, running PAC ROM 23.0 and Android 4.2.2) from their nightly basket builds (I tried to install the November 19th build.) The installation itself goes off without a hitch, as does the GApps installation. However, after installing it (cleaned out the cache and Davlik cache prior to installation, installed GApps after installation), I get multiple error messages. The keyboard process has stopped working, and android.process.acore have stopped working (tells me to blame Tyler.) The device also seems to be laggy in general, and when I try to launch the Phone app, it says it is not installed.
I just want to be able to use 4.3 and PAC ROM's newest features.
If someone can help me resolve this issue or link me to a stable but updated build of PAC ROM, that would be great.
Thank you!
D3xus said:
Hello there.
I recently tried to install the most recent version of PAC ROM for my Galaxy S4 (Sprint, SPH-L720, running PAC ROM 23.0 and Android 4.2.2) from their nightly basket builds (I tried to install the November 19th build.) The installation itself goes off without a hitch, as does the GApps installation. However, after installing it (cleaned out the cache and Davlik cache prior to installation, installed GApps after installation), I get multiple error messages. The keyboard process has stopped working, and android.process.acore have stopped working (tells me to blame Tyler.) The device also seems to be laggy in general, and when I try to launch the Phone app, it says it is not installed.
I just want to be able to use 4.3 and PAC ROM's newest features.
If someone can help me resolve this issue or link me to a stable but updated build of PAC ROM, that would be great.
Thank you!
Click to expand...
Click to collapse
You need to do a full wipe from PAC23 to 4.3 (factory reset in recovery)
Figures. :/
What app should I use to backup the contents of my phone to use after the update (messages, apps)
I'd like to share my experience solving some basic problems with my nexus 4 running cm11, and 10.2
I had problems with the video freezing when shooting video
I wanted to improve the sound quality because I stream google premium and couldn't find a solution until recently
And had a rebooting problem in the end which I solved.
My nexus 4 worked perfectly running cm until I did the 4.3 update in november. After that the video would freeze when I was shooting. wouldn't happen all the time but would happen sometimes. I did everything, factory resets, reinstalling gapps, restoring the camera app, wiping data. Nothing worked. Even updating to cm 11 did nothing to change the situation. After having to go back to stock because of another problem I ran into -- installed Franco kenrnel on cm 11 and they aren't compatible -- I discovered that the video camera was still freezing. So I discovered it had nothing to do with cyanogenmod roms. Someone suggested flashing the separate photosphere gapp package along with the full gapps package and funny enough that solved the problem.
http://forum.xda-developers.com/showthread.php?t=2397942
I don't know if the recent updated photosphere gapp corrected a problem or what. But. Shooting Video now works.
I switched to omni rom because I wanted to use the franco kernel to adjust my sound settings, in my search for sound quality improvement but the omni rom was a real challenge and was plagued with bugs and wasn't for me. But stuck with it because of the franco kernel.
I then discovered that hells-core kernal did the same thing and works with cm11 so switched back to cm11 the stable snapshot version from last week and installed hells-core kernel. My phone started to reboot capriciously every 10 or 15 minutes and tried everything to correct that, eliminated data from apps, fixed permissions -- nothing worked, but finally decided to flash the latest cm nightly to see if the problem wasn't related to the version of the rom I was running .
When I flashed it, I wiped cache partition, delvik cache, and formated data , reflashed full gapp package plus the photosphere gapp. I didn't flash hells-core again. Maybe that was causing the reboots. I don't know. Everything now works perfectly. No more random reboots, the video camera seems to work fine, I discovered that the cm kernerl does have one volume gain adjustment and am now using viper4android effects equalizer that has gain control for both volume, bass and treble and everything is great. and my sound quality is probably as good as it will get on a nexus 4.
I spent an inordinate amount of time trying to resolve these problems so hope this is of some help to others.