I just bought this phone today, everything's been going great until I received a phone call on the stock rom. The phone instantly froze and rebooted, I tried placing a call once it restarted and the same thing happened. I was planning on flashing a rom anyways, so I flashed to Dynamic Kat. The same exact thing happens, the phone works flawlessly until you try to place a call.
Anyone ran into this problem and know a fix? Thanks for any help.
Related
Ever since i updated to v4.2 of Cyanogen I've been getting a weird problem. I'll get a call and cannot unlock my phone, I can't see who is calling, it just shows the desktop. If I answer I can talk, but the phone will reboot itself in the middle of the call.
I've tried to wipe/reinstall and it just started doing this again. Anyone else run into this kind of problem?
i believe there were issues regarding this posted in his thread. however, are you running the newest build? if not i would suggest updating, once again. there has been few bugs patched up! also, run fix_permissions....worst case senario completely start over, that means rc29+.
Hey guys, I've got an odd problem and am hoping somebody out there can help me out.
I bought a nexus one a while ago and promptly rooted it and installed cyanogen's 5.0.6 mod. I followed the guide on XDA to the letter and had no problems at all. Cyanogen's mod was great and the trackball alert pro was amazing.
My brother saw my phone and after his jailbroken iPhone called it quits he bought one offline from www.google.com/phone. He asked me to unlock it and put cyanogen's mod on there.
I used the same files, that I did for my phone, and followed the same steps listed on the guide to the letter, just as I did for my own phone. I didn't change one thing in the process.
However, after booting past that lovely cyan colored x and getting into the phone, it would randomly reboot, and then get stuck at the solid X logo, forcing me to take out the battery. I would take it out, wait 30 seconds, put it back in, only to have it happen again.
I thought it was a wiping issue, so I redid everything to no avail. I even put everything back to stock, and tried once again doing everything I had done for my phone to no avail. I can't figure it out and it's frustrating me. All the files are the same that I used on my phone, nothing is different except the phone, yet whenever I install the Rom, it randomly reboots and gets stuck on the solid X logo.
So, as you can see I'm at a loss. I'm not sure why my phone works and his doesn't. FWIW his phone DOES NOT reboot when on stock everything, only when a custom ROM is on it. Also, I set my phone back to stock everything and re-rooted/flashed and have had no problem, yet when I do the same steps on his phone, random reboot/frozen.
Can anyone out there help?
Nobody?
SphericalPuma said:
Hey guys, I've got an odd problem and am hoping somebody out there can help me out.
I bought a nexus one a while ago and promptly rooted it and installed cyanogen's 5.0.6 mod. I followed the guide on XDA to the letter and had no problems at all. Cyanogen's mod was great and the trackball alert pro was amazing.
My brother saw my phone and after his jailbroken iPhone called it quits he bought one offline from www.google.com/phone. He asked me to unlock it and put cyanogen's mod on there.
I used the same files, that I did for my phone, and followed the same steps listed on the guide to the letter, just as I did for my own phone. I didn't change one thing in the process.
However, after booting past that lovely cyan colored x and getting into the phone, it would randomly reboot, and then get stuck at the solid X logo, forcing me to take out the battery. I would take it out, wait 30 seconds, put it back in, only to have it happen again.
I thought it was a wiping issue, so I redid everything to no avail. I even put everything back to stock, and tried once again doing everything I had done for my phone to no avail. I can't figure it out and it's frustrating me. All the files are the same that I used on my phone, nothing is different except the phone, yet whenever I install the Rom, it randomly reboots and gets stuck on the solid X logo.
So, as you can see I'm at a loss. I'm not sure why my phone works and his doesn't. FWIW his phone DOES NOT reboot when on stock everything, only when a custom ROM is on it. Also, I set my phone back to stock everything and re-rooted/flashed and have had no problem, yet when I do the same steps on his phone, random reboot/frozen.
Can anyone out there help?
Click to expand...
Click to collapse
I had the same issue with mine and a buddys N1... not sure exactly what to do but I wiped right before I put cyan on and the again right after and if started fine after that... wipe it was much as you do when you poo! lol worked for me! GOOOOD LUCK!
Thanks for the tip. When My brother gets off work i'll try it on his phone and let everybody know the results
-------------------------------------
Sent via the XDA Tapatalk App
zippa71385 said:
I had the same issue with mine and a buddys N1... not sure exactly what to do but I wiped right before I put cyan on and the again right after and if started fine after that... wipe it was much as you do when you poo! lol worked for me! GOOOOD LUCK!
Click to expand...
Click to collapse
Well I tried your suggestion with no luck. It rebotos and gets stuck at the X after about a minute inside the homescreen
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
Hello lads! The last few days I have been trying to fix a huge problem with my Galaxy S4 i9505. I had been using the Google 4.4 rom for almost a month without any problem. One day, when my phone was low on battery it shutted down and I plugged it in my charger to power it on again. When it turned on I was prompted to the screen you see when you use the 4.4 rom for the first time. I had all my apps but everything was resetted. Every setting, all the app data, messages, etc. I thought this was a one time thing so I used about an hour to get everything back to normal again. Then the next day, same happened again. Phone turned off because of low battery, and everything was reset. I tried to google it but with no luck, so I did a factory reset and flashed the newest Google rom (4.4.2) with a new kernel called Ktoonsez. Got everything back to normal again and used my phone for a couple of hours before it just suddenly shutted down once again, but this time with almost full battery. When i tried to turn it on I was stuck on the Google loading animation and had to reflash 4.4.2. It turned back on and this time I decided to let the phone stay stock to see if any of my problems was caused of my apps or settings. It lasted for 2-3 days before the same thing happened again... I tried to flash different modems, other roms and firmwares but nothing have helped so far. I am also prompted with a message each time I turn the phone on which tells me that com.android.phone has stopped working. I have tried several factory resets, wiped dalvik, wiped cache, but still has the same problem... I have now given up trying and wonder if anyone of you know what I can do to fix the problem? Any tip is much appreciated and I hope to hear from you! Thanks!
edit: figured out I posted this is the wrong forum as this is for s4 active and i have a i9505. Sorry! Anyway, please comment if you know how to fix it. Thanks!
Fredrik
This problem started on her unrooted Amazon Prime version. What I did was I went ahead and unlocked the bootloader and installed the 7.4.2 OTA without ads as well as rooting it. That actually worked for a few days, but whenever she gets a phone call, the ringing started to be mute once again. She has claimed that she's tried restarting it, but to no avail did this work. How do I fix this infuriating software bug?
DragonfireEX402 said:
This problem started on her unrooted Amazon Prime version. What I did was I went ahead and unlocked the bootloader and installed the 7.4.2 OTA without ads as well as rooting it. That actually worked for a few days, but whenever she gets a phone call, the ringing started to be mute once again. She has claimed that she's tried restarting it, but to no avail did this work. How do I fix this infuriating software bug?
Click to expand...
Click to collapse
Did you try changing changing the ringtone. Blu usually is fussy when it come to ringtones,. Just reset phone and stick to default ringtone for while to see if it helps
At the time we had tried this, it did not resolve the issue at all.