im currenty using liteROM 0.9.0 first 3 days work fine, but after i found this problem.. can anyone help me..
+1.
My phone.android repeatedly shut down in Gingerbread. Only fix i could find was upgrading to ICS.
when arldft
Hmmm.... that is weird, i´m also using LiteRom 0.9, never had that issue, first time i flashed the custom rom i did see that message a couple of times, but no big deal just reeboot and no probs. after that though i decided to install the rom from scratch, never had an issue with it since. only problem ive had is the toggle for gps sattelites and mobile connection giving me some issues, nothing a reeboot cant resolve.
my advice would be to backup all your info & apps and start from scratch. or boot to CWM and fox permissions.
hope i helped
I had similar issues with GB. I was using the latest Osimood rom. Upon receiving a call, my phone screen would go blank (the way it normally does when switching to a call) but then it would freeze. The ringtone would not ring and after a few seconds of this, the phone would go back to the last app and the network signals would be gone. After a few more seconds, the network signals would be back. The same thing would happen if I received another call. The only fix was to reboot the phone.
The annoying part was that there would be NO way for me to tell who was calling me since I would never see their name and no entry would be made in the phone log. I didn't have any success with treating that problem. While it didn't happen very often, the few times it did would be very annoying since I'd often find out several hours later that I had missed an important call.
I've just switched to Pacman rom today in the hopes that this was a rom issue and will be gone now. Let's see.
Related
Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...
it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...
Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.
Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse
Try reinstalling the ROM or installing another ROM.
hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long
Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't
Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App
Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin
Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App
Figured I'd cross post this as it seems to be an issue for a few people. ( http://forum.xda-developers.com/showthread.php?t=1951699 )
I've noticed this issue since first getting my S3 in July. So I do know it happened with 4.0.4 and now with 4.1.1. I've never used the "Stay Awake" option in the dev options and it still remains off. I've had the issue with both "Smart Stay" on and off. I've tested it with all screen time out times, as well as going through the trouble of factory resetting the device and nothing changed. The only solution I've found is reboot the phone and it will work again for a day or so until I notice it again. Very annoying and would love to find a solution to this!
I just started having the same issue. I was using Black Jelly's JB ROM for like 2 weeks without the problem then I flashed the LK3 modem and it started happening. I did a full wipe and flashed the ROM from this thread - http://forum.xda-developers.com/showthread.php?t=2034844 last night and I'm still having the problem. My touch key lights stay on all the time too along with the screen not timing out.
My S3 has been stock from day one. I also got mine a few days after it was released, starting to wonder if its a hardware issue?
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
I've noticed it on a replacement S3 I got when it wasn't an issue with the prior one. The new one (as with the old) is stock, updated to JB when I got it. GFs phone does the same.
geiswiz said:
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
Click to expand...
Click to collapse
This is interesting. I've been noticing this issue ever since I updated to 4.1.1 some weeks back, but had not considered any connection with missed calls. Among the dozens of reports I see online (with not a single one resolved), I found another thread that mentions it happening after missing a call (or receiving an SMS).
I completely wiped my phone and flashed a stock 4.1.1 rom two days ago and noticed this happening again while sitting at my desk today. I did miss a call earlier, so I think there is something to that suspicion; I rebooted the phone and sure enough the screen and touch keys timeout as they should. I just received a text and that didn't trigger the issue, but I'll have to wait til I get another call to know for sure, or until I get home and have the time to test it.
Ok, yep, it definitely is somehow triggered by missing a call, but it seems to only happen some time later after the last reboot. I had rebooted my phone yesterday, missed a call not too long after, and the keys and screen would shut off normally. But I just missed a call right now and sure enough it's acting up again...
My problem started about 4 days ago. It started with random stops of the phone reception and call disconnections. After that, my SMS app (Pansi SMS) Started collapsing every time I tried to use it (the stock app also collapses). Now the situation is like this: My phone reception goes on and off, every time it goes on I get a message that says "com.android.phone has stopped unexpectedly. Please tell HTC about this problem. To help...send and error to HTC" and then I can neither `Force close` or `Tell HTC`. Immediately after I press force close the airplane turns on and off (I see it in settings->wireless & networks page) and the reception goes to zero. and this is the loop. every couple of seconds all the process repeats itself. it's very frustrating.
I'm using Virtuous glite v.2.0.1 at the moment. The problem started when I was using a Virtuous sense rom. I changes a few roms to see if that's the problem but with no use. I'm pretty sure my hardware is fine because I get a signal, and I can connect to wifi.
Help please?!
I encountered a similar error whilst using ILWT. The ROM is probably liable here. I suggest flashing another ROM and posting this problem on the ROM thread. I flashed Andromadus Beta 5 (http://forum.xda-developers.com/showthread.php?t=1349864) afterwards.
Hello,
I was wondering if someone could help me out. I am having issues since the past few days with making and receiving calls. The phone FREEZES while on a call, (there is no set time as to when this happens) and I have no choice but to take out the battery and put it back to restart the phone. It is becoming a quite a nuisance and was wondering if this was due to some application or something else I'm unaware of. I had a phone protector and I've taken it off since the past few days but it still freezes while on a call. FYI...I use the GO Dialer EX for the calls, have avast mobile security installed as a virus protection. I have *TheCollective* AoCP - CP5.3 installed with AOSP JELLYBEAN 4.2 Linux 3.0 Ktoonsez kernel.
Any help would be appreciated. This freezing is driving me insane...
harryrasul said:
Hello,
I was wondering if someone could help me out. I am having issues since the past few days with making and receiving calls. The phone FREEZES while on a call, (there is no set time as to when this happens) and I have no choice but to take out the battery and put it back to restart the phone. It is becoming a quite a nuisance and was wondering if this was due to some application or something else I'm unaware of. I had a phone protector and I've taken it off since the past few days but it still freezes while on a call. FYI...I use the GO Dialer EX for the calls, have avast mobile security installed as a virus protection. I have *TheCollective* AoCP - CP5.3 installed with AOSP JELLYBEAN 4.2 Linux 3.0 Ktoonsez kernel.
Any help would be appreciated. This freezing is driving me insane...
Click to expand...
Click to collapse
Such problems can be something hardware. I had a similar issue with my old cell phone, freeze for 10-15 seconds maybe, and then reboot. There was an error in the Sd-card. My suggest is to use some app for check/scan your sd cards for errors. If your sd card is corrupted for some reason, or has some files corrupted, read or write from it can produce unpredictable results, like a freeze.
Yeah, could be any number of things, including a corrupted file on your SD. You can check for errors on your SD by following these steps:
http://www.ehow.com/how_8748172_check-integrity-android-sd-card.html#page=0
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I thinks it probably your under clock or overclock try messing with your CPU speeds
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks folks for your suggestions. I have used the avast internet security app to scan the apps as well as the SD card and it hasn't found anything wrong. I did a fresh install of a new ROM today (AOKP) and it did the same thing today. While making calls it was freezing up at random times. I did try one though, which is use the PHONE icon as opposed to using the GO Dialer EX and it didn't hang but I may have to try that several times to come to come to any conclusion.
Would formatting everything and doing a fresh install fix it?
harryrasul said:
Thanks folks for your suggestions. I have used the avast internet security app to scan the apps as well as the SD card and it hasn't found anything wrong. I did a fresh install of a new ROM today (AOKP) and it did the same thing today. While making calls it was freezing up at random times. I did try one though, which is use the PHONE icon as opposed to using the GO Dialer EX and it didn't hang but I may have to try that several times to come to come to any conclusion.
Would formatting everything and doing a fresh install fix it?
Click to expand...
Click to collapse
so you're saying that when you use the included android dialer you have no issues? so we can conclude that go dialer is the culprit?
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
and formatting everything might fix things. if you're going to make the effort, i'd wipe data, cache, dalvik, format /system, flash rom/gapps, wipe data and cache again.
its also common to have issues when not coming from stock when you flash an aosp-based rom
I am having the same issue. Phone freezes sometimes during calls. I can finish the call, but then the phone is frozen, I have to take the battery out or wait for phone to restart after a while...Also, sometimes looks like proximity sensor doesn't work, as it doesnt turn on screen in call when I remove phone from ear.
Alcatel X'Pop, Stock Android 4.1.1, exdialler installed(not go dialler)
Same issue here on a GS4 with latest CM11 nightly and no custom dialer. Been having the issue for a couple of months. I've tried different ROMs including back to stock with the same issue. I though perhaps it was a defective proximity sensor but several appss show the sensor working correctly. Open to any ideas!
hi guys, i got a d855 and i have some issues which i think they may be stock rom's bugs and i d like to hear your opinion. I have the latest ota V10h-EUR-XX btw.
1) Every time i restart it appears in the notification panel the "voice mate" shortcut. I remove it using the edit at far right but still it reappears every time i reboot the phone.
2) Sometimes after an unanswered call or message the screen turns on as usual but it doesnt turn off. Ofc i ve selected to shut off at 30 seconds from the settings. Even if i change the settings to like 15 seconds the screen still wont turn off unless i manually lock it. This problem fixes if i restart the phone.
3) Every time i boot my phone i get this message: "unfortunately the process com.google.process.gapps has stopped"
So is there someone else who experiences these kind of issues?
wow, these 3 bugs are new to me. haven't experienced any of those at all.
I'm on V10J global though.
You're having permissions issues.
I'd bet my left testicle that a fresh flash back to stock will fix all 3 of your issues.
+1 on the voice mate .. irritating ~
I've encountered the screen on issue - although not only did the screen stay on after a missed call, the phone also became and remained completely non-responding, no screen input registered. Had to reboot manually. It happened only once in 3 weeks though.