hi all
i have been using nand android builds since day one , and in most of the builds i am having this same issue
sometimes when i receive a phone call the system just hangsout and then gives me a force close msg for the phone application !!
either way , if i force close or not , no further phone calls can be answered and the phone will freeze for about 30 seconds with every call
also when this happens the volume buttons wont modify the volume for the media anymore and the phone wont give any sounds
so is there something i can do to get rid of this ?
i tried android builds based on 2.3.3 and 2.3.4 , miui , sense , no sense , and i have this issue with all of them
again , it happens like 10% of the times
hope i get an answer to this
I want to ask what exactly rom are you using (does it use newest tytung r10 kernel?) and tell you that I have not been experiencing these issues with NexusHD2 2.8 rom (2.3.4).
fpu
i tried typhoon , rafdroid , ndt miui , and plenty more and i think typhoon and ndt miui has the latest kernel
have you ever tried receiving a phone call while the camera application is running
this seems to trigger the issue many times , not always tho
if you have the call recorder running turn it off. it was causing me lot's of problems.
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
domenukk said:
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
Click to expand...
Click to collapse
+1 Same ****...
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
I just recieved a phonecall without problems.
Flashed the .12 radio from http://forum.xda-developers.com/showthread.php?t=611787&highlight=radio
however... My rom feels a bit slower now.
I am playing with it now.
Maybe clearing Dalvik cache will help. Or the issue comes back... Will see.
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Synthezys said:
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Click to expand...
Click to collapse
Switching Radio to something.12 did the trick for me.
No problems for two days now.
domenukk said:
Switching Radio to something.12 did the trick for me.
No problems for two days now.
Click to expand...
Click to collapse
Leo_RADIO_2.12.50.02_2 - is this good?
Synthezys said:
Leo_RADIO_2.12.50.02_2 - is this good?
Click to expand...
Click to collapse
Yes that's it. Works fine for me
Mea culpa just today I had the same issue, for first time.
It's nothing major and reboot made it work fine again, but breaks my belief in HD2 as perfect, native-like Android device.
[email protected] said:
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
Click to expand...
Click to collapse
Beside changing of radio, THIS seems to be interesting.
I'm on MAG but considering switching to cLK (for many reasons - fastboot support being one, second that I don't need 99% of MAGLDR features).
Let's see how it all pans out ;-)
fpu
It just happened again! On the new rom... :/
There is a thread, however, stating that it's due to skype.
This can very well be true.
http://forum.xda-developers.com/showthread.php?t=1164058
but I need skype to stay on contact with my girlfriend... why can't android support skype natively instead of sipthings? -.-
Well still... anyone tried clk (instead of magldr) and skype?
Disable "Audible touch tones". It's under Sound in Settings, it did the trick for me.
I thought this was against robot voice?
well what ever. let's give it a try. Thx
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
An0n1mUs said:
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
Click to expand...
Click to collapse
For me recieving a call does nothing but a very bad noise. hd2 nearly freezes after that. I cannot hang up most of the times. If I somehow manage to, phone app forcecloses and connection cannot be reestablished until I pull out the battery...
Good old Robotvoice. I wish that was my problem.
i have switched to cLK about 3 days ago and till now i have got no problems at all
Related
HI,with respect to user's , admins n DEvelopers i would like to say SOD might be due to the sleep time settings (image attached)in brightness.i might be wrong or might not be,if im wrong sorry in advance n would req. the admins to delete this thread,Tnx to all..
EDIT :
Use mattcfroyo 1.4 (with latest cotulla zimage) or DARKSTONE froyo v1 latest(384ram enabled)
[my preference] with windows rom: chuky gtx/chukydroid/miri17.6
and radio 2.10.50/2.12.50 no echo no robovoice no sleep of death evrything is fine
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Stoferr said:
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Click to expand...
Click to collapse
thats y i let this info to other users let see what happens to them,n i dont hav n SOD problem but i have robotic voice :"S too bad cant get rid off it,can u sggest me a ROM,m using updated tmous ROM n radio 2.12.50.xxx.. tnx in advance.. and lets see what others say with sleep turned of.. and please do share your results... thank u..
Im testing it right now, so far no problems, but it seems randomly whener SOD appears, so i'll just test it a little longer.
Im using the european HD2.
hmm.. Lets see the results of other users also... and please do share ur findings...
P.S: m using TMOUS HD2 and waitin when i can get rid of robotic voice.
Damnit just got it! Well, seems that this won't help It was a nice try tho
i have never had sleep of death its gta be rom and radio related
i tried to help all... thats all.. but tnx for tryin... but i dont hav SOD either.. now dloadin maatcleo+froyo v1.2 n gonna test if it has SOD..
robotic voice is killing me :'(
I've had sleep of death with basically every android build out there.. i don't think it's a setting in my personal opinion. i think it is because it's still in develoupment and the drivers aren't 100% yet.. and i'm sure in time it will be fixed.
I tried it on zimage 7/25 and still have SOD .Some claim they use the new zimage without SOD ,no matter what I do it won't wake up.
the battery is horrible on 7/23 zimage and carrying the charger in my pocket all the time is a pain.
Off topic: I loved the notes on dna u had there
The "Turn screen off" setting is active in my WM. Using German T-Mobile 1.72 ROM, Radio 2.10.50.19_2, Dan's Froyo V1, zImage 25/7.
Using this combination for two days now and didn't have a single SOD during this time... only two or three times a freeze for few seconds, but afterwards Android resumed working.
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Been using dans13 build with cotullas no speddy zimage. My Rom right now MIRI 17.6 and Radio 2.12.50.26. No SOD report here just couple of freezes now and then. Good battery life. I have to say that I disabled the Auto lock in Windows with HD2 tweak. The first time I tried android on hd 2 i got the SOD, but with this combination and disabling the auto lock been running smoothly. just my 2 cents.
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
Well what I don't get is when I started trying Android on my tmo hd2 I didn't get the sod but now I do. if its the screen why did it start now?
Daaaaaaaaaaaaaaaaaaaamn waiting for new zImage... Seems that I have a sharp panel... How can I check this?
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
well now im using miri's v17.6 rom wid radio 2.12 on tmous HD2 no SOD till now although sleep is active in WM...
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
I've read the same but i think a lot of it is just down to individual ROMs & radio builds, as when android started on hd2 everyone said turn off backlight but mine was never on high nor did i alter any settings as when haret kicks in it turns off all windows functions altogether so you can't have any cross network/OS issues, winmo is supposed to be cut off. although saying that if android is only running off sd how can you remove sd and still run android for 1hr or more? but that's a different topic.
If you have a Tmo US HD2 just use Cotulla's 7/23 zimage and you should not get sod. If you use 7/25 zimage, you WILL experience sod! If you experience sod with 7/23 zimage, then the likely culprit is your sd card. Reformat and try again. If that doesn't work, you need to try a different card.
I am using the 7/23 with chucky's rom, and i was fine all day yesterday but this morning i got 4 sod in 15 minutes, and everytime i rebooted after that. I changed my Radio to 2.12.50.02 and i turned off the sleep thing in WM, and so far haven't had a sod in about 3 hours.
okay so i've used the phiremod skinnyEVO1.5 and Mdeejay eVo Sense Stock and i've had the same problem with both. Whenever i make a phonecall/receive a phonecall, as soon as the person and i end the call my phone goes completely unresponsive. the screen goes completely black, and none of the hardware keys light up
the only thing ive found that can get the phone to come back 'to life' so the speak is to call the phone again and end the call on my phone with the end button.this doesnt always work though.
im running the Chunkydroidrom in WM and have radio 2_12_50_02
i even updated the kernel on the Mdeejay build and it still happens
is there anything that can be done to fix this?
please help me guys
different build, but same issue, nexus one by ummmmmmmmm matc forget which version. radio 2.15, wm chunky gtx sense with that CHT 2.0 i think..................
so far our windows mobile rom is the same cook, could be where to start im about to change my winmo rom
i just changed my windows mobile rom to ozdroid and im still having the same problem, and when i use the included bootloader i get robotic/froggy sounds in phone calls. maybe its not running clrcad correctly so ill try it the old fashioned way and see what happens
please
bump
can someone pleasee help?
good luck in finding help. Ive had some of the same issues i believe. My phone will completely freeze during a call for now apparent reason. it'll working fine in the call in the just freeze during my call. I tried different winmo roms that are suggested for droid builds. i believe i tried every radio available for tmo and about every build of driod and the problem is still there. It may run fine for a day then it starts freezing. I've posted a question about this yesterday and 97 people have viewed it and one person suggested i return the phone. I don't believe that its a hardware issue, more like a software issue. I guess i better learn how to pull the logs and then i may get a reply. i just haven't found a place that it explains it well enough for me to do it myself. My persistence will prevail though, cause I'm addicted.
Well please if you ever figure it out please let me know as this can get quite annoying
Sent from my HTC HD2 using XDA App
Disable Auto-Rotate in the Settings>Display.
See if that helps.
I had the same problem. I have Advanced Task Killer installed and it was set to kill apps on screen off. I turned off the option to kill apps on screen off and so far it solved my phone call = unresponsive phone.
I have theese issues only if i have certain call recorder softwares installed .. try uninstalling them , and if nothing helps delete ur data.img and do a fresh start(u can back it up tho if it prooves unusefull)
@souljaboy
what exactly do you mean by certain call recorder softwares installed? such as which ones?
@JonSolo
i disabled auto rotate and i still experienced the problem during phonee calls
@mike91t
i changed my auto kill to every 4 hours, so i'll let you know what happens with that over the course of the week
Same problem here, I've turned off screen autorotate, and I don't have any task killers installed. Everything works fine, and even a call or two, then it stops working and audio during calls doesn't work, and phone app becomes unresponsive.
have you tried a different radio rom?! maye 2.14 will help.
fruchtfliege said:
have you tried a different radio rom?! maye 2.14 will help.
Click to expand...
Click to collapse
well i waws thinking about changing to 2.14 but the android build im using recommends certain roms for best performance so i was going to keep using the radio rom and see if anything improved, so far i dont really think its working, so i might change to 2.14 because people seem to be having the less problems with it
Hello all. Im using Chuckdroid rom with the new radio 2.15 (although the problem still existed with 2.14) and Mdeejay Froyo revolution android.
I had this issue spring up unexpectedly. I had been using Mdeejay's previous version for a day or two with no issues. Then all of a sudden the audio stopped working. I tried updating the radio first to 2.15 from 2.14. Then I tried rebooting after initial launch because it was Froyo. Then I tried updating the Android version to the newer one Mdeejay had. Still nothing.
When it first boots there is sound if I press volume up. Then nothing.
Any thoughts? Is this because of Froyo? Am I missing something?
I jsut changed out the Android version again to: CMYLXGOs.Droid.RedTopia.v1.0.1. It is still not working. I have no idea where I messed up here. Im still searching! Anybody?
Bump. Still having issues guys.
First things first.... Do you have working sound in WM?
adamsweeting said:
First things first.... Do you have working sound in WM?
Click to expand...
Click to collapse
Yes, the sound is working in WM.
worldishis said:
Hello all. Im using Chuckdroid rom with the new radio 2.15 (although the problem still existed with 2.14) and Mdeejay Froyo revolution android.
I had this issue spring up unexpectedly. I had been using Mdeejay's previous version for a day or two with no issues. Then all of a sudden the audio stopped working. I tried updating the radio first to 2.15 from 2.14. Then I tried rebooting after initial launch because it was Froyo. Then I tried updating the Android version to the newer one Mdeejay had. Still nothing.
When it first boots there is sound if I press volume up. Then nothing.
Any thoughts? Is this because of Froyo? Am I missing something?
Click to expand...
Click to collapse
Same here, after boot Sound is working, leave it for sometime then NO Sound at all, even media players, youtube, phone calls, Sound Just stops working, cant even call or hear anyone when I use the dialer, as if there is something that Kills Sound.
Desire HD 3,7
Any Fix or workaround? How can I get the Sound to work again?
Willy318is said:
Same here, after boot Sound is working, leave it for sometime then NO Sound at all, even media players, youtube, phone calls, Sound Just stops working, cant even call or hear anyone when I use the dialer, as if there is something that Kills Sound.
Desire HD 3,7
Any Fix or workaround? How can I get the Sound to work again?
Click to expand...
Click to collapse
Im at a loss. Ive never had an issue I couldnt figure out until now. Next thing Im going to do when I get home is change the kernel. If that doesnt work then a different rom. If that doesnt work, I guess change the radio to 2.12 or before. Other than that I dont know what to do. Maybe format and start over.
I wish somebody would weigh in with this.
blah blah blah
Hey guys, so I've been having s slight issue latley. When someone calls or texts me, there isn't any ring tone playing and the volume is set to 100% and mostly the only way to get the sound back is reboot the device.
Any fixes?
Also, today I had a call from my dad and I accepted the call and I couldn't hear anything. When I called back I didn't hear any beeping either. I rebooted my phone and then it worked. What's up with that?
Should I switch Roms? Or is there something else I could do? Thanks!
Sent from my Nexus One using XDA App
I had the same problem. Kept happening intermittently. Tried different roms...didn't seem to fix it. Tried several fixes I found in the forum but no success.
Finished up reflashing the standard htc wm6.5 rom back on and tried boyppc's gingerbread rom http://forum.xda-developers.com/showthread.php?t=970542 and haven't had the problem since.
I did try another android rom before this one....the first call I got coming in didn't ring, so I don't think the 6.5 rom was the issue. Why boyppc rom works when some of the others didn't I don't understand...but it did....so I'm happy.
blankers said:
I had the same problem. Kept happening intermittently. Tried different roms...didn't seem to fix it. Tried several fixes I found in the forum but no success.
Finished up reflashing the standard htc wm6.5 rom back on and tried boyppc's gingerbread rom http://forum.xda-developers.com/showthread.php?t=970542 and haven't had the problem since.
I did try another android rom before this one....the first call I got coming in didn't ring, so I don't think the 6.5 rom was the issue. Why boyppc rom works when some of the others didn't I don't understand...but it did....so I'm happy.
Click to expand...
Click to collapse
hmm..that's weird. i'm gonna try CM7 and then i'll see if i have any problems, thanks for a reply though!
I'd be interested to know how you get on. I'm very reluctant to try any others now that mine is working so well.....
I have found that I don't use windows much any more so I might try a nand sd build later on......
blankers said:
I'd be interested to know how you get on. I'm very reluctant to try any others now that mine is working so well.....
I have found that I don't use windows much any more so I might try a nand sd build later on......
Click to expand...
Click to collapse
As soon as I get some time ill switch over and tell you how that goes!
Sent from my Nexus One using XDA App
So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.
Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.