com.android.htcdialer has stopped responding - Sprint HTC One (M7)

For some reason, playing around with (flashing) different ROMS, sometimes I get the error "com.android.htcdialer has stopped responding..." and NO data follows not matter what I do to try and fix this; deleting caches, switching different signal modes, etc.! What causes this? Anyway, I've found that the error returns even after flashing a different ROM and/or kernal or even restoring my backup. I've also found that flashing the radio again fixes this. Just in case anyone finds themselves in same situation.

jasonbiggs said:
For some reason, playing around with (flashing) different ROMS, sometimes I get the error "com.android.htcdialer has stopped responding..." and NO data follows not matter what I do to try and fix this; deleting caches, switching different signal modes, etc.! What causes this? Anyway, I've found that the error returns even after flashing a different ROM and/or kernal or even restoring my backup. I've also found that flashing the radio again fixes this. Just in case anyone finds themselves in same situation.
Click to expand...
Click to collapse
I started receiving this error after I attempted installing a rom that said "Sprint support" but didn't actually support Sprint. After that, I started getting the dialer error whenever I use a Sense based rom. I re-flashed the radios. Sense based roms still don't work, but Cyanogenmod 11 does. Today, I tried flashing the Viper rom and the problem returned. I restored Cyanogenmod, the problem resolved without having to flash the radios again.
Have you learned anything more about this issue? What needs to be flashed to restore/reconnect the dialer??

I believe at this point your only option is to reflash a stock RUU....I had the same issues with mine and reflashing stock was the only thing that fixed it for me

jasonbiggs said:
For some reason, playing around with (flashing) different ROMS, sometimes I get the error "com.android.htcdialer has stopped responding..." and NO data follows not matter what I do to try and fix this; deleting caches, switching different signal modes, etc.! What causes this? Anyway, I've found that the error returns even after flashing a different ROM and/or kernal or even restoring my backup. I've also found that flashing the radio again fixes this. Just in case anyone finds themselves in same situation.
Click to expand...
Click to collapse
Found that this works too:
http://forum.xda-developers.com/showthread.php?t=2634256

Fount 1 trick that fixes this problem.
So I turn on airplane mode, then I make hot reboot, after reboot turn off airplane mode and bam it works

Mine does this if i flash any rom but viper rom or any kernel. i Need a fix

Related

G1 reboots when enabling WIFI

When I try to enable WIFI on my G1, for a couple of seconds it says: enabling WIFI, but then the phone becomes unresponsive (for about 1 second) and it reboots.
IIRC the problem started when I upgraded to the new CynogenMod ROM (4.1.99, but not sure), but it doesn't seem to be linked to the ROM.
I have always used CyanogenMod and update with every new version.
I tried to go back to the default HTC rom, but this doesn't solve the issue.
Does anyone know what may cause this or give me some tips on how to debug this?
I tried to run 'adb logcat' but it shows no info.
The exception browser in the CyanogenMod is also empty.
I don't know what else I could try.
Some extra info:
HSPL 10.95.3000
Radio 2.22.19.26I
CynogenMod ROM 4.1.99 is not the newest. Wipe, flash the htc image, flash cyan's newest and try wifi again.
No, I know, but I think that's when the problems started.
Latest version I installed was 4.2.13
I have installed the RC7 dreaimg.nbh now (used to root the G1), and when I try to enable WIFI on this rom, the phone doesn't reboot, it keeps working, but I get an error saying that WIFI could not be started.
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
mattb3 said:
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
Click to expand...
Click to collapse
This is consistent with my experience as well. By far, the VAST majority of spontaneous reboots that have occurred on my phone have been when using wifi. Some of the older Cyan ROMs were really bad about this, but this continues to occur (although much less frequently) regardless of the ROM. I am presently using SuperD and have had one reboot in the past week.
This seems to happen most often when using the wifi heavily; for instance, I get a reboot probably every 3rd or 4th time when I'm doing my weekly podcast downloads. I don't remember any reboots when just surfing the web or downloading apps, though.
I have never had this happen when I was running cyan.
Are you wiping everything? Even EXT and dalvick?
Are you using any other apps when this is running and rebooting? Perhaps an offending app?
You should also open ADB and run ADB Logcat and try to replicate the issue and try to get a log submitted so the dev can help determine what is causing this issue.
I wiped everything and even without any apps installed, it just reboots.
adb logcat doesn't show a thing when the phone reboots, it just exits.

[Q] Wifi broken, need help please

After a few days running Dlev's 4.2 ROM, my wifi stopped working suddenly. When I try to turn it on it says error or unable to start wifi. I've exhausted several initial options I began walking myself back through various ROM's back to the original 2.1 stock ROM. Without success I even performed a master clear and several reflashes of the orininal stock ROM, nothing is working. I tried FXR Wifi fix and rescue. Does anybody have any ideas on what I should do?
Thanks,
-Digitalchaos
Kernel?
What kernel were you running with the custom ROM? Talon's being updated really frequently, so if it's Talon, you might try the latest version of that (0.4.4.22, as of this writing)
digitalchaos said:
After a few days running Dlev's 4.2 ROM, my wifi stopped working suddenly. When I try to turn it on it says error or unable to start wifi. I've exhausted several initial options I began walking myself back through various ROM's back to the original 2.1 stock ROM. Without success I even performed a master clear and several reflashes of the orininal stock ROM, nothing is working. I tried FXR Wifi fix and rescue. Does anybody have any ideas on what I should do?
Thanks,
-Digitalchaos
Click to expand...
Click to collapse
Did you try rebooting your router or device that gives you wireless signal? also see if other devices can connect.
It was Talon 0.4.4, but I've gone all the way back to stock ROM/kernel etc and that makes me think that this is a HW malfunction.
AT&T had me reboot the router too, my laptops are able to connect just fine. It's not really a connection problem either, Wifi will not turn on at all.
I called Samsung and they want me to ship them the phone, still debating that one since I will have to go without a phone.
-digitalchaos

[Q] Wrong rumrunner... now I have no service...

Phone was working fine, could make calls/text, and could use data. I unfortunately didn't realize that the different versions of rumrunner were specific to your phone's software version, and instead thought they were simply different revisions of the program. I realized this after waiting about 20 minutes as it kept restarting my phone and kept saying ''waiting for device'', and decided to try a different version of the program. At this time I noticed I didn't have data and couldn't make calls. I was hoping that running the correct rumrunner would fix this problem, but that doesn't seem to be the case...
I've tried installing CM and seeing if maybe the stock rom was somehow corrupt, doesn't fix the issue. I'm back on the stock backup again, and still having the issue. I tried flashing the radios for my software version, doesn't seem to have any impact...
I thought it would make more sense to post this question in the actual rumrunner thread, but new account limitation are not allowing me to do so. Hopefully I can get a solution to this problem...

[Q] Various Issues - Tried different ROMs but issues remain

Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc

[Q] Faulty hardware or something else? Please help!

Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
koolkeith said:
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
Click to expand...
Click to collapse
maybe your sim is faulty. try to get a new one from your provider. or it just has a bad contact in your phone.
about the lagging: did you try a clean flash? is your storage full? my phone gets pretty laggy when my storage is nearly full..
Hey thanks for your reply! However I dont think its the sim card, and as I mentioned I clean flashed several times with several twrp version and also twice with wiping all data on my sdcard...
Sorry if I can't offer a concrete solution, but I had similar issues (especially the first one, but also lag when switching networks) on my HOX+. Turns out it was the sim.
Try to test another sim before returning, and at least try a sense based rom. Since you say that it works without problem for a few days with Liquidsmooth 4.4, and then it starts breaking again, it may be rom (aosp?) related. But then again, it may be just random.
Hope you figure it out soon
Thanks akpe! I ordered a new sim card, if that doesnt help I suppose its something hardware related...
Well, the new sim card didnt help. My problem seem very similar to this: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/
Basically my whole radio disconnects and restarts itself when turning off wifi. Reading that androidpolice thread leads me to thinking about flashing an earlier firmware, from 4.2.2. I have no idea which one, or if I can use the one in that thread or not.
Any suggestions? I'd appreciate it, googling for hours and reading catlogs for days isnt getting me anywhere..
HELP!
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
akpe said:
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
Click to expand...
Click to collapse
Hi akpe! I took your advice and am now running ViperOne 7.0.2 and so far it WORKS! So it seems it was indeed that google bug. HUGE THANKS!
Is it possible to have the aosp lockscreen when at the same time using a pin? I can't seem to figure that out.
Thanks again!
Glad it worked
As for the lockscreen, no idea mate, I'm using the stock one :/ Ask around in the ViperOne thread, maybe someone there knows
Ok, thanks again!
Another thing I cant find is profiles? Need it to make whatsapp notification sound silent when listening to music..

Categories

Resources