Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
jtleniger said:
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Try using a different recovery. I've had that problem before, baseband and IMEI were shown as unknown and com.android.phone would force-close constantly. I don't know why the recovery would cause that, but switching recoveries worked for me.
I had this same issue yesterday, very strange that I would see this listed here about the same time. I haven't done anything different, that I haven't done before. Then I flashed the stock T-Mobile rom and it still kept doing it. Apn settings disappeared when this happened.
Related
I have unlocked my bootloader and rooted my phone. Still running stock 2.2.1. Seems that about one month again I noticed that intermittently all of the previous notifications will return. I can clear them and they will stay gone for a while but will return later in the day. Also noticed that super user has begun to give me a "stopped unexpectedly" error. This seemed to start about the same time as the notification problem. Don't know if the 2 are connected. I've tried to do a search but did not find anything about the notification problem. This is forcing me to think about getting off my butt to install a custom ROM. Any suggestions before installing a custom ROM?
Jackie
jbeenemd said:
I have unlocked my bootloader and rooted my phone. Still running stock 2.2.1. Seems that about one month again I noticed that intermittently all of the previous notifications will return. I can clear them and they will stay gone for a while but will return later in the day. Also noticed that super user has begun to give me a "stopped unexpectedly" error. This seemed to start about the same time as the notification problem. Don't know if the 2 are connected. I've tried to do a search but did not find anything about the notification problem. This is forcing me to think about getting off my butt to install a custom ROM. Any suggestions before installing a custom ROM?
Jackie
Click to expand...
Click to collapse
The newest update of super user is causing many issues, suggested not to update.
I have superuser versions 2.3.6.1 and 2.3.6.3. I will try a reinstall of 2.3.6.1.
If still have problems then will try 2.3.6.3. Will not allow an ugrade until I see a newer version than the one out now.
Thanks
Jackie
Hey guys, its my first post on here and I was hoping to get some help with my device. (Yes, I've searched extensively over the internets. No, I can't find anything related to this issue for the One X)
So let me start from scratch. About a month or so ago, my phone started rebooting randomly, I have been using ViperX 2.7.1 by Team Venom since day one of getting my phone and only started experiencing these issues after upgrading my hboot to 1.31, switching to MaXimus and returning back to ViperX. If it was the occasional reboot, I wouldn't be half as annoyed as I am this very moment. Unfortunately, my phone does not ring when I get a call. Does not ring, screen doesn't even turn on, does not notify, nothing. I called it from another number, did not ring, tried turning the screen on, did not turn on, just rebooted. This does not happen all the time, but has been happening a lot recently. So far, I have fresh installed ViperX numerous times, (wiped cache, factory reset, wiped dalvik cache and full wiped from the ViperX aroma installer) thought maybe an app was misbehaving so fresh installed from the play store instead of Titanium Backup. Even tried switching ROMS but I can't for some reason. Tried installing CM10 the other day, didn't go past the white screen. The good people on androidforums.com told me that I need a different boot.img for newer hboots so I got that, but the CM ring at startup freezes followed by a reboot. Switched to ViperX 3.2 (JB) couple days back hoping this issue wouldn't follow me here as well, but alas, it still has. Then yesterday, I thought upgrading my hboot and wiping my phone the way up'ing the firmware does might fix it, so I up'ed my hboot to 1.39. (strangely though, I still have my files on my sdcard) I followed this guide: http://forum.xda-developers.com/showthread.php?t=1920060 Only step I couldn't follow was the adb reboot oem-78, I got some strange error (did not happen when I up'ed to 1.31) After getting 1.39, I flashed ViperX 3.2 again but I still have this error.
I'm completely out of ideas and am really close to giving up and selling my phone. Any help/advice on what I could do would be greatly appreciated!
Original post: http://androidforums.com/international-tegra-3-one-x-all-things-root/667919-random-reboots.html
Disable AOSP lockscreen in tweaks.
stifler05 said:
Disable AOSP lockscreen in tweaks.
Click to expand...
Click to collapse
Woah, no way. Is that it? It worked perfectly fine before I up'ed my hboot to 1.31 (always used the AOSP lockscreen). Have you encountered a similar issue? I'm trying this out now, will keep you posted.
Yesterday my gps wasnt working at all. It would not lock on no matter what I did. I was on a custom rom and I tried wiping my data/cache, reinstalling maps (just for giggles), and a multitude apps from the market that help deal with gps problems (gps fix, gps status, toolbox, etc).
When all this didn't work I decided to odin back to the last official JB update and still no gps. On a whim I decided to odin back to an ICS firmware and that made my gps work. I have no idea but it did. I then odin to UVDLJC, installed TWRP's most recent and restored my backup of the custom rom I was using in the first place and gps now worked.
While I'm happy as heck that my gps is now working and that it was not a hardware issue I'm extremely curious what happened.
I have flashed many roms lately and I cannot think what a custom rom can do to gps to hose it or if it was just one of those things. I would of thought that when I originally did an odin to UVDLJC that would fix the issue but that didn't. Whatever the flash to ICS did fixed it but what in the heck could that of been?
I figure if I can find out or get an idea what happened then I can steer away from flashing certain roms, or just be prepared that flashing any roms at all can make this happen again.
Same here.
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Typically, it's been when people are going from 4.2 to 4.1.
Zza1989 said:
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Click to expand...
Click to collapse
Well I used odin to flash an T999_UVALEM which was a prerooted ICS rom. After booting it up I checked to see if GPS was working and it was.
I then used odin again to flash T999_UVDLJA which is a JB rom and booted it up also and saw that gps was working. Then I just restored a backup of a room I had been using and GPS still worked.
I've been out of town and noticed that after flashing a few roms that gps wasn't working so instead of doing all the above stuff I just flashed a cm10 rom. I believe I either used a cm10 nightly (or maybe 10.1, memory is hazy) or LiquidRom and that got the GPS working by just doing that. Not sure if that will work for you but you could always backup your setup using TWRP's latest and then flashing a cm10 rom and seeing if gps is working and if that fixes it then you could then just reboot and restore the rom you are currently on and that might fix your gps for you.
http://forum.xda-developers.com/showthread.php?t=1949687
Hi all,
Not sure if anyone can help.
I have seen loads of posts about the com.android.phone has stopped working problem but none are like what happens to my phone.
I have a rooted note 2 and running jedi x17 rom (4.1.2 based on the standard touchwiz) all works fine no problems.
I want to go to a 4.3 rom like cm/pacman/pa etc but whenever I flash the rom and reboot after 2 min the com.android.phone has stopped comes up, but only once after I reboot, everything works fine and I can get on the Internet and make calls etc, it's just annoying.
I have even gone back to unrooted stock and started again but the problem still happens, any help would be great.
I'm on the EE network in the UK, I was wondering if Apn settings could be a problem.
try after flashing to wipe cache and do a factory reset, see if that works.
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Vipery said:
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Click to expand...
Click to collapse
try the KDZ. if it continues then it must be a hardware problem..
raptorddd said:
try the KDZ. if it continues then it must be a hardware problem..
Click to expand...
Click to collapse
Thanks for reply, i have fixed the problem. Just pull out and put in the battery, idk what happen it seems to be solved now.