[Q][HELP] Incoming and sending calls - Desire HD Q&A, Help & Troubleshooting

Hey ive currently started receiving an issue where my phone screen turns off when you ring someone or receive a call, its like it automatically senses something touching it as if it was on my ear.
I've reformatted and tried it with cm7 nightly it worked but now its doing the same thing.
Also the initial HTC screen freezes whenever i try and boot into the recovery.
Thanks in advance

what radio and/or kernel did you flash prior or did you have this problem fresh-out-of-the-box?

I didnt flash a kernel or radio, prior to installing the new cm7 nightly, i had the cm 6 stable
plus i tried to install gapps a numerous amount of times and it still wont install my market :/

Related

[Q] Text Sound Notifications

Every since installing CM7 I would initally get text and email sound notifications but after some time this stop working. I have tried serveral different ROMS with no problems. I LOVE the new CM7 and would like to conitnue using it. It is the best ROM I have tried yet.
I have tried everything I know to try, format, wipe, erase, reboot nothing seems to work.
Does anyone have this same problem and if so how do I correct it?
#1Jinx

Dialer/phone FC every rom

So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
jr8801 said:
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
Click to expand...
Click to collapse
Looks like it might be a kernal problem. Have you flashed back to the stock kernal? If not, I'd look there first
yeah i flashed stock kernal as well...problem still persist
uninstall Google+
no google + never have had it.
Have you tried flashing CM7 Alpha #2? I had that same problem with Alpha #1 release then flashed #2 fixed permissions. Then at first start up i rebooted with GPS on and voila! No more phone FC.
I started with Alpha #1 where the problem started flashed over #2 fixed permissions and same problem. thats when i started flashing the other roms to try to solve the problems but this hasnt helped. So i odin back to stock. flashed stock kernal and stock recovery. and i still have the problem.
What sucks is im just graduating college and im starting to receive calls from future employers and i cannot talk for more then 2 minutes before my phone decides to shut off.
So any other advice???
bump it up. Any help please...::
what it is doing now update: I click on a contact or type a number and press call and the screen turns black except the status bar. soft keys dont work, hard keys dont work. phone is a fail. people can still hear me and i can still hear them but the phone is unusable and i have to pull battery to get out of the black screen.
This was doing it on every rom and i have now put beastmod v2 4.0 still no luck :[
I just received my White GS2, finished the OTA update.
And yes, the dialer FC on me every single time once I push the hangup button.

[Q] Microphone stops working with latest roms

Right now my G2 is running Cyanogenmod-7.1.0 RC1. For the last few months any time I try to update past this version of the rom I lose my microphone. It works absolutely fine with 7.1 but when I go to 7.2 it breaks. For example, When I am on a call I can hear the other person but it is silent on my end. Voice recording programs do not work either, all that it records is a low level of static noise.
I have also tried CM9 and audacity beta4 with the exact same results. When I flash my phone back to 7.1 everything is fine.
Is there some way that I can flash just the old microphone drivers onto the new roms? I am competent enough to follow instructions but not enough to start breaking builds apart for the individual pieces so I don't know where to start.
I have always done a full wipe on everything before I flash.
Does anyone have any ideas? Thank you!
Currently I am running:
Radio: 12.52.60.25U_26.08.04.30_M3
Kernal: [email protected] #1
Mod: Cyanogenmod-7.1.0 RC1 vision
Build number: GRJ22
a
Didn't try any of those,
but this rom:
http://forum.xda-developers.com/showthread.php?t=1492461
works great on my HTC Desire Z with absolutely no issues
It does take a bit of customizing.
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
haymaker said:
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
Click to expand...
Click to collapse
Hi! Do you solve your problem? I have the same thing there. All the CM roms above 7.0.3 not working with microphone. Do you have still the Cyanogenmod-7.1.0 RC1 file rom and can you upload for me?
Thank you!

Random reboots // Not receiving calls

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.

[Q] CM11 No Sound/Mic, Force Closes, Etc

Hello fellow XDAers,
I recently went through the flash dance for my Sprint Blue L710 S3 16GB to switch it from some old version of CM 10(.2?) to the latest nightly of CM11. I essentially followed this guide to get my phone up to the latest and greatest and flashed pa_gapps-modular-micro-4.4.4-20141110 to give the the level of GApps I'm comfortable with.
Now I tried to follow the same guide with my wife's Sprint "White" S3 32GB L710. Right off the bat the phone wouldn't boot after the oneclick flash - it got stuck on the loading screen (I waited 30 minutes on the boot screen before giving up... twice). Only after I flashed Philz 6.5.14 recovery was it able to properly boot into the OS (potentially a PIT problem, but all 32GB PIT files seem to be removed from the web). In the stock ROM, phone mic, sound, voice dialer, and Google Search all worked (and I tested this several times during recovery attempts). It noticed it hadn't taken advantage of all 32GB available on the phone, so it decided to expand the partition itself (bonus?). Then I flashed the latest nightly CM11...
Once booted, I cannot get the dialer to behave correctly. I installed the GApps after booting up the ROM once (and tried again on a fresh install by installing it prior to first boot). Immediately after boot, using the Phone app and dialing a number the screen turns to a blank (black) screen. The phone dials fine, but once connected to the number being dialed, there is no sound or mic. When I open the Sound Recorder app, it says "internal application error" and "microphone may be in use". When I try to do "OK, Google", it acts like the microphone isn't able to be accessed. When I open Apollo to listen to anything, DSP Manager force closes. It's as if the hardware can't be accessed by the ROM. SMS, cell network, WiFi, and GPS all work. It seems familiar to this CM thread, but the same steps aren't working for me.
I've flashed a few ROMs based off of AOSP (Slim and AOKP mainly), but none of them seem to allow me to utilize the mic and speaker of the phone. Only ROMs based directly off of sto k ND8 let me "phone out". For instance, stock ND8 works as well as Wicked-X.
I've flashed multiple ways, cleaned/formatted several times, and tried all sorts of tricks to get this to work on my wife's phone. I'd like to believe I've done enough research to feel like coming to the community is my last resort. As a software developer myself, I know there's probably something simple I've missed, but can someone please help me figure out why my "blue" L710 is working but not my wife's "white" 710?
Thank you very much in advance.

Categories

Resources