Hi,
So yesterday i was walking the dog listening to some music when my phone just died. I booted it back up again, listened some more and it died again. When this happened i was running version 1.2.0 of said mod, so i decided to try the latest.
Seems like i have this issue there aswell Everytime my phone goes into lock it shuts down. Anyone have an idea what can cause this? my phone is almost a year and a half.
Update: Removed my memorycard and no problems so far, will try to format it and let you know.
Update 2: Formatted SD-card, seems to be working again now.
Update 3: Nope, its back again. Any ideas?
Thanks to everyone for any help on this
Juji
Try installing the test version of 1.4 and do a full wipe before that.
You should also try and flash any other ROM (maybe even stock) to make sure it's a ROM issue and not some HW fault on your phone.
Do we have any chance to have a 2wcr kernel for this great ROM?
I have the same 1-2 times per day after calling with
Virtuous Quattro RC3
so maybe a bug in ICS ?
Have been running without any force shutdowns for over 24hours now, so it might have been temporary for me atleast.
I got no problems so far with ICS on DHD, flashing from 1.2.0 to 1.4.0 without full wipe. I think different phones get different issus with same ROM. Maybe the installed apps are a reason for that.
I had that bug, but I was running Gingerbread at the time. The problem worked itself out, around the same time I upgraded the SD card. That might be a cause, maybe re-seat the sd card? Might be loose or something along those lines.
I'm running 1.5.0 and mine keeps saying no network and keeps rebooting itself????
Related
Okay guys this one has been screwing with me for a while now and is getting progressively worse.
I have a launch day EVO 0002 hardware and I believe an Epson panel but don't remember that one 100%
My evo was running great up until the 31st/1st. I put on a CM6 rom and a snap kernel. Phone was running fine then started lagging horrible so I did a reboot.. Phone went into bootloop. So I went into recovery wiped data/ cache/dalvik 2 times (clockwork recovery).
Restored the phone to Freak E Froyo which I had been running for 2 weeks. Next day I tried the senseless Freak E Froyo and wasn't as much of a fan of it so I installed AVA v6(then flashed king kernel 8 over the top) then the touchscreen issues arose. My screen would think it is being touched when it is not pages would flip, apps would open and no buttons would work. When i hit the home button it opens whatever is on the left of the screen and when I push the back button it opens whatever is in the middle of the screen.
So I nandroid'ed to My Freak E froyo after wiping all again. Still did it. Flashed CM6 6.0.0 after wiping all. Still same problem but worse and even more noticeable on CM6 .
I then switched to AMON RA recovery, tried the same thing: wiping all 4 times, reinstalled CM6, same problem.
Tried reinstalling stock 2.2 odexed and rooted was fine until about 5 hours after running then almost every time I could only use the phone for about 6 seconds and the touchscreen would become unresponsive...
I am thinking it is a piece of a kernal not flashing correctly so It is causing problems maybe?
If not that do you think it could be a CPU problem itself? Maybe going out and unable to hold up anymore and causing freezing?
Any suggestions will be tried. If not work then...I will most likely try a 2.2 RUU and format my sd card and see if that does anything.. and lose root/nand unlock
Yes my v002 EVO had the same issue and all 002 are novatek but I dont think its a screen problem.
I gave up trying to figure it out but I know with mine if I ran ANY rom that came out before the 1.47 OTA then it would NEVER have this issue..
If I ran ANY rom after the 1.47 OTA then it would always do it..Sometimes it might take hours for it to happen but it will..I'll bet yours is probably the same way.
The offical HTC 2.2..yup same thing
The offical HTC 1.47 OTA..yup same thing and this is when it started.
I wiped/flashed/wiped whatever you can think of and the problem NEVER went away on any newer ROM's but as soonas I load a older ROM it never happened.
Look for the EVOlution v9 ROM..Its the ROM I ran until I exchanged the phone..I'll bet if you load that ROM you won't see a single touch screen issue.
Just my 2 cents but save yourself the headache and exchange that damn phone..
That is what I will most likely do tomorrow. Will take it back to stock to do it tonight but it is just weird because I never once had a problem until the bootloop. My buddy who has an evo we got em at the same time store ..etc.. His alot of times will do this and he is not rooted or anything...Just hoping they dont give me any problems tomorrow at sprint...
I've been using my desire for about 1 year now and never had any problems until I decided to go back to Leedroid gingerbread rom and install the patches for A2SD+ with ext 3.
I was having restarts every 10-15 minutes on Leedroid, went back to CM7, currently on cm7 7.0.2 and I'm still getting restarts when I wasn't previously.
I have asked this question before and thought it was an issue with the SD card. Now the reason I thought it was the SD was when I was having loops of restarts I would take it out and it would be quite stable for a while. Formatted everything (SD and internal + cache) put on the latest radio rom and then put on the latest CM. Seemed to run fine for a while and then started restarting again. It locks up on the HTC screen occasionally and requires me to pull the battery.
I've noticed that it only happens when I'm using 3G internet connectivity. Just recently it tried to get a lot of updates and would start downloading them only to restart. It does eventually get the updates though.
To test this I can start watching a youtube video and it will crash. For example I just watched 1 minute of one video before it crashed, after reboot I started youtube again and it crashed immediately.
Can I stop log cat removing all the logs when the device restarts so I can have a look what's going on? Any other ideas on how to diagnose or fix would be much appreciated.
What's your radio?
My Radio version is
32.56.00.32U_5.17.05.23 and I'm running CynogenMod 7.0.3
I used something else before I switched to leedroid an old one, I changed it to go to Leedroid then changed it to this hoping it would help.
Flashed newest correcspondig ril 2.2.1003G?
Thread for radio/ril here on xda:
http://forum.xda-developers.com/showthread.php?t=902752
No I have never flashed a RIL before, didn't even know what these where. I'll give that a shot and see what happens.
DeliveryNinja said:
No I have never flashed a RIL before, didn't even know what these where. I'll give that a shot and see what happens.
Click to expand...
Click to collapse
RIL (by System of a pWne!^)
Radio interface layer. This is a layer between the Radio and the ROM. It communicates with the hardware over the Radio and supplies an interface for the ROM so it can use the hardware. This is similar to a driver.
Whenever you flash a new Radio, you should also consider flashing the corresponding RIL for it. This makes sure, the Radio is getting adressed correctly.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=805247
I was running the RIL suggested above yesterday, had about 11 hours and no issues, updated all my apps, was watching youtube etc.. I was trying to do stuff that usually would make it crash. Eventually I turned on my wifi at home and as soon as it came on the phone rebooted. It then proceeded to reboot every time I tried to go on the internet, with either 3g or wifi, I tried about 3-4 times. Leaving it with internet off for about 30 mins, I came back to it and it started working on wifi fine. Strange. TL;DR ril didn't seem to fix it. Seems like if I can get it back to stock I can go to the shop and change it.
Dear fellow Desire owners,
i really like my InsertCoin rom but it's getting on my nerves lately. It crashes or hangs frquently. I see the lockscreen but nothing happens except when I pull the battery.
This has been happening more and more. Sometimes I notice my phone has been hanging for an our or so. I then have to remove the battery to get it working again.
I first thought it was the radio so I flashed it with version: 5.17.05.23 but things are getting worse. This morning I had to use the navigation but it kept hanging. At last I reverted to a NANDROID backup I made a week ago.
My question now is: how can I find out what is buggering my phone? Is there a log or an app that can do some troubleshooting? Is it an app that makes my Desire so miserable? How can I know this? Please help me.
Thanks!
Go back to stock rom to find out if it's the rom. If problem persits, call HTC.
TouchPaled from Oxygen with Transparent XDA App
Before you reflash again your Desire, you can check and format your sdcard.
Or change a new sdcard and faster speed.
If the same issue, it might be hardware issue on Desire.
Because I used IC ROM from 1.1.0 to 1.1.4, every version is so far so good.
So what you're saying basically is that there's no way of checking logs or troubleshooting or whatever?
So I did a full whipe and installed v1.1.3. Which went well for a week or so, but then it started crashing again on a daily basis.
I went ahead and bought myself a class 10 8GB sdcard. I just copied everything and did a nandroid restore. See if that works... And if that doesn't do the trick i'll try a full wipe and fresh install again.
Same problem
Hi,
I have exactly the same issue, could you give me the result of your experience with your new sd card ?
It's an old post but I would like to have an answer to my problem.
Thanks
All versions of insertcoin Rom were perfect... What class card do u use???
I use class 4... Works perfectly.....
Hello!
For some time now my phone's been rebooting itself completely random it seems. I just got it back after sending it away to get this issue fixed. Obviously the "repair" didn't really do anything at all. All they did was to flash the latest software apparently.
I got quite fed up with the crashing and rebooting stuff, and figured that it wouldn't hurt to try to flash a custom ROM, in this case I chose to root the phone and try MiUi. I had no clue wether it would solve the issue I'm having, but I figured it was worth a try. So i rooted the phone and flashed the latest version of MiUi (1.11.18).
At the start it seemed like it had worked, and had stopped the phone from crashing. But after some time I realized that the issue is still there, only difference now is that it ONLY crashes when I lock the screen with the Power-button. EVERY SINGLE TIME I do this, in a matter of minutes it will either reboot or just turn black and totally unresponsive. Only way to get it on again is to take out the battery and put it back in.
This is starting to annoy the **** out of me, so I talked to my brother for advise this morning, and he told me to wipe my Dalvik Cache. So I did, and nothing changed, the phone keeps on living it's own life.
I have absolutely no clue what info you guys might need to help me with this, but I'll start with this:
Phone: HTC Desire HD
Android-version: 2.3.7
Kernel-version: 2.6.35.14-cyanogenmod-g319b6e2
ROM: MiUi 1.11.18
Also, the motherboard's been switched once, cause of another issue that is now gone.
ANY help is appreciated, I just want to be able to use the phone normally!
EDIT: Also it seems that the phone won't reboot or crash whenever it's charging.
Sounds like a hardware/software issue your best bet is getting a replacement and re rooting .
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.