Develop Bugs

[Q] Phone disconnects right after pressing call.

This is happening to 2 people at work with stock Incredibles w/2.2. I have never experienced this on my phone which is rooted with stock 2.2 ROM.
You press Phone, either dial a number or click from the list, it starts to dial and then immediately disconnects. Rebooting the phone will correct it until the next time it fails (Usually once a week).
Tried using Task Killer on one of the phones but it didnt make a difference.. Can someone point me to a thread or help out? I can't seem to find this issue, or my keyword searching stinks

Does the screen go completely black and freeze up when this happens?

Nope, everything seems to work except the phone. I should problem check Phone Identity in About Phone when it happens I guess.
I'm surprised that there aren't more replies to this thread because 1 out of 3 DINCs at my work are doing it.
Sent from my ADR6300 using XDA App

Noone else has this problem? Very odd...

Some times i cant pick up the.incoming call.

My defy is having one problem. Its actually random. Sometimes when a call comes, i am not able to pick it up. The touch simply wont work. Then i have to cut the call using the power button and call them back.
Sent from my MB525 using XDA App

Are you using SetVSel? If yes then what settings are you using?

Im getting rid of mine because of the same issue. It seems to randomly break during some incoming calls. Sometimes the touch sensors stop working, sometimes it fails to to bring up the answer/reject lock screen and just brings up the normal one. Other times it goes into a frenzy of randomly pressing the buttons and touch screen all by itself while ignoring anything I do to try and prevent it. Its a great device, but as a phone its been crap for me.
I dont use setvsel because it caused issues with the graphics on my defy, even at 850 it caused corruption and freezing on anything 3d. I had the call answering issues before rooting and unstalling setvsel btw
Sent from my MB525 using XDA App

LetoKynes said:
Are you using SetVSel? If yes then what settings are you using?
Click to expand...
Click to collapse
Yes i am usi.g setvsel. So u r saying it could be the problem? Nywy by settings what you meant? Is it the voltage levels and frequency?
[email protected]
[email protected]
[email protected]
Sent from my MB525 using XDA App

obscurant1st said:
Yes i am usi.g setvsel. So u r saying it could be the problem? Nywy by settings what you meant? Is it the voltage levels and frequency?
[email protected]
[email protected]
[email protected]
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeap that's what I meant.
Well I'm not entirely sure, but I remember someone mentioning he had trouble picking up calls because his frequency was too low but yours seem fine.
Have you tried disabling SetVSel to see if it works OK without it?

XDA app? where did you get it?

Sometimes i cant able to lift the call
even i am not able to lift the call sometimes the touch is not working at the time by clicking the power button then the call is ending.

Yeah, i got it from the market.
Sent from my MB525 using XDA App

But its not happening always, till now it has happened for me like 5 times in 3 months! so i dont think i will b able to check it after switching the setvsel off. I will have to stop it like 1 month or some to confirm it! any other option?

obscurant1st said:
But its not happening always, till now it has happened for me like 5 times in 3 months! so i dont think i will b able to check it after switching the setvsel off. I will have to stop it like 1 month or some to confirm it! any other option?
Click to expand...
Click to collapse
happens here too, no root, no overclocking tools. plain stock defy but happens
with launcher ex as well. mostly when on the charger or been not in use for a
few hours.

oh ok, so its not the problem of overclocking/undervolting! So I'm happy. I thought like I will have to remove the root and all!
But still, why is this even happening??
Will it get fixed on the froyo update?? :/

obscurant1st said:
oh ok, so its not the problem of overclocking/undervolting! So I'm happy. I thought like I will have to remove the root and all!
But still, why is this even happening??
Will it get fixed on the froyo update?? :/
Click to expand...
Click to collapse
in the german android community it's only listed as an eclair problem so hopefully it is solved n froyo. i am still waiting for the update.

philofax said:
in the german android community it's only listed as an eclair problem so hopefully it is solved n froyo. i am still waiting for the update.
Click to expand...
Click to collapse
Wow, thats a real relief. Thanks man.
Sent from my MB525 using XDA App

I have this problem with mine. Totally stock and it didn't happen until AFTER I updated to Froyo. It has happened about 5 times now.

You sure it will be fixed in froyo? Yesterday my boss was calling me to discuss something imp and I could not pick up the call because of this damn issue, I had to disconnect the call with the power button and called him back :-|

vikrambharadwaj said:
You sure it will be fixed in froyo? Yesterday my boss was calling me to discuss something imp and I could not pick up the call because of this damn issue, I had to disconnect the call with the power button and called him back :-|
Click to expand...
Click to collapse
Did you miss my post? I never had this problem until AFTER I updated to froyo. Now, I am experiencing it on occasion. This would lead me to believe that something else is amiss.
Are you guys using a screen protector?

someAZdude said:
Did you miss my post? I never had this problem until AFTER I updated to froyo. Now, I am experiencing it on occasion. This would lead me to believe that something else is amiss.
Are you guys using a screen protector?
Click to expand...
Click to collapse
, then it could be something else.
And well, I am not using or will ever use a screen protector! I simply don't like them. idk why!

I think its just a problem with motoblur, since i'm using custom roms i never had that issue
Sent from my MB525 using Tapatalk

D3rR0fl3r said:
I think its just a problem with motoblur, since i'm using custom roms i never had that issue
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
But tbh i don't think Indian defy has motoblur installed in it! At-least I haven't seen it yet on my phone!

i have indian rom , but i have faced this issue...and i dont know why it happend....faced 2 to 3 times now...hoping to get an solution.....one solution is just lock and unlock it again by press and release pow button i think it solves the issue of random screen freeze

Problem with calling

Problem: i call somebody, calling is delayed for about 5 seconds, same with whenever i end the call, the screen stays for about 5seconds.
And sometimes, when the screen is off and when i answer the call, it becomes a miss call. Anybody experience the same?
Sent from my HTC One X using xda app-developers app

Me. I think this is something that happens on all smartphones. They are computers with the ability to make calls, not dedicated phones with the ability to compute... But I agree, that delay in starting/ending calls should be seriously adressed. It costed me already a few money!

Dusturm, You are on stock or custom rom? I'm using ARHD
Sent from my HTC One X using xda app-developers app

I have a problem too with calling and hanging up, doesn't happen all the time.
Sometimes when I make a call my phone will try to ring the number and then just hang up and not even ring and this is with full signal.
If I try to end a call the screen stay on and pressing the end call button doesn't respond I have to wait for the other person to end the call or my screen responds after a while. I'm on stock, I think this is normal for HTC my old desire used to do this too.

*elmo* said:
Dusturm, You are on stock or custom rom? I'm using ARHD
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Stock.
Sent from my HTC One X using xda app-developers app

I am using MIUI rom,having no such question

dusturn said:
Stock.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I'm using custom. It means it's not custom ROM problem but
HTC...

Yeah I experience this, sometimes I answer the call, but it goes into a missed call.
Other times I cannot end the call as already stated.
And other times when trying to call, it will make no noise and then cancel the call.

Till now now solution :crying:

I have the same issue. any ideas how to solve it?

htcxone said:
I have the same issue. any ideas how to solve it?
Click to expand...
Click to collapse
NO

The same. Any solution?

Probable solution...
I've read somewhere in the HOX forums about problem concerning the kernel. The guys there adviced to change the kernel. I have the same problem with the end call especially and will be trying to fix it by replacing the kernel this evening. If this succeeds I'll write immediately here to give you the solution! :good:

Go to ur key pad, type the number u want to call, press the menu key.... Check weather u hv enabld called delay, deactivate it n see
Hit THANKS if m any help
~RR

See this
Hit THANKS PLEASE
~RR

...
It's not the "calling"! It's the "end calling" I have no issue with clicking call button and activating it! The problem is with the END CALL button.

Oooo.... Ok get a factry reset... Will solve this bug...
Click THANKS button if I helped, or u liked my post.
Will be honored.

possible solution
Guys, when you were flashing rom into your device last time did you perform a full wipe/factory reset? Cause I didn't and when I flashed exactly the same rom (and ver.) couple of hours ago but this time full wiping I got rid of the "end call" bug! Backup everything important with titanium and full wipe!

Same issue here. Started suddenly last week (after 4 months of owning hoc). Had args 9.3.2 at the time. For week all was fine then it started for no reason after few apps updated. Flashed 9.7.0 with full wipe. All ok till installed all my apps. Done again same. Done again same. Done again and installed apps one by one testing. Managed to install all apps all was good. Next day started again.
Sent from my HTC One X using Tapatalk 2

ruscik said:
Same issue here. Started suddenly last week (after 4 months of owning hoc). Had args 9.3.2 at the time. For week all was fine then it started for no reason after few apps updated. Flashed 9.7.0 with full wipe. All ok till installed all my apps. Done again same. Done again same. Done again and installed apps one by one testing. Managed to install all apps all was good. Next day started again.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Do you have any application that is linked to the dialer? Such as a different dialer or a contact management app etc..?

[Q] Samsung Galaxy Note 2 GT-N7100 freezes for few seconds every time

Samsung Galaxy Note 2 GT-N7100 freezes for few seconds every time when i place a call or end the call.
It takes around 15 seconds when i place a call and then i have to wait for it till it comes,
same thing occurs when i end the call.
After i click end it freezes and takes 15-20 seconds to end the call which ultimately gets added in my total call duration seconds.

akshay1008896rana said:
Samsung Galaxy Note 2 GT-N7100 freezes for few seconds every time when i place a call or end the call.
It takes around 15 seconds when i place a call and then i have to wait for it till it comes,
same thing occurs when i end the call.
After i click end it freezes and takes 15-20 seconds to end the call which ultimately gets added in my total call duration seconds.
Click to expand...
Click to collapse
Are you on a stock ROM? Is it for your region? I would try either updating the software (if an update is available) or try a different rom and see if still has the same behaviour. Also, have you checked your phone bill see if you actually get charged for those extra 15 seconds? If yes, it could be a network problem, in which case I would contact your network operator first. And you could try with a different SIM card (different number if possible), see if you get the same behaviour.

Yes I'm om stock rom...I haven't rooted my phone...and yes those extra seconds are charged in my bill..also I don't think so that its the issue of network as when I place a call that time also it gets freeze and aftet few seconds I see calling screen. .
Sent from my GT-N7100 using xda app-developers app

OK then try with another SIM card - it's the simplest to do. If you get the same behaviour try another ROM.

You could also try to enable the option "The power key ends calls" under Settings > Accessibility > Answering/ending calls. Maybe that helps you, since you can end the call even with the phone still on your ear.
Also you could try cleaning the data on the Phone app and related apps (Phone, SecPhone, Dialer Storage). If it doesn't help, make a Nandroid / titanium backup of your data, factory reset the phone and see if it still hapens with it in a "brand new" state. If it doesn't, selectively restore the titanium data (user apps only, and data only of the few system apps that matter).
Hope it helps.
Cheers.

Hey thanks for suggestion but I tried cleaning data and cache of all I three (phone,sec phone and dialer storage) but it didn't helped.
Any thing else I can do but expect rooting my phone.
I dont want to root it.
Sent from my GT-N7100 using xda app-developers app

akshay1008896rana said:
Hey thanks for suggestion but I tried cleaning data and cache of all I three (phone,sec phone and dialer storage) but it didn't helped.
Any thing else I can do but expect rooting my phone.
I dont want to root it.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I had the same issue. After a call my n7100 with PAC Rom Android 4.2.2 freezed for a few seconds.
But now it's freezes permanently. Only reboot helps take it back to life. There is no other problems.
I tried to move to another ROM - Root Box. Same ****.
Did you figure out something on this issue?

WonderMr said:
I had the same issue. After a call my n7100 with PAC Rom Android 4.2.2 freezed for a few seconds.
But now it's freezes permanently. Only reboot helps take it back to life. There is no other problems.
I tried to move to another ROM - Root Box. Same ****.
Did you figure out something on this issue?
Click to expand...
Click to collapse
i'll reply to myself. Unfortunately It's SDS. Moved to 4.1.2 and Perseus Kernel. Now it's ok. Good by AOSP :crying:

WonderMr said:
i'll reply to myself. Unfortunately It's SDS. Moved to 4.1.2 and Perseus Kernel. Now it's ok. Good by AOSP :crying:
Click to expand...
Click to collapse
There are still AOSP roms you have not tried, I am sure. PA in the original development section (now with source built HALO) for example, or the Asylum "Naughties", or even something AOKP-based like the new resurrection remix betas (4+).
Happy flashing!

Issue got solved.
It was an app causing issue.
Youlu app which actually caused the issue.
Sent from my GT-N7100 using xda app-developers app

[FIX] [GSM] BT Temp Fix for CM9 and CM9 based ROM users

Only for CM9 and CM9 based ROM users :cyclops:​Did your phone just switch off and wouldn't turn on completely when turning on the bluetooth one day? :crying:
Do you really need your data/messages/settings/alarms/call log back? :crying:
Do you really need to access the internet or call someone urgently? :crying:​:fingers-crossed:!! HERE'S THE FIX !! :fingers-crossed:​OK, So, it's actually not a fix but a way you could get back your precious messages (if there were any), settings, alarms, call logs, etc.. everything!!
It has happened to me the third time while using AOKP Milestone 6 for the HTC One V..
So one day you just turned on bluetooth and your phone got switched off and got mad . It started getting switched off within 10 seconds as soon as it started. You have important messages, etc. whose backup you don't have. You're going mad, you just don't know what you should do within those 10 secs.. DO THIS -
First, of all, I'm not any big man to even give out a fix or something.. But what I did really helped me to get back my data..
I was using CM9 UnOfficial for the One V and there came a bad day on which my phone entered a bootloop and I was ruined with all my customizations..
I loved CM9 so I tried AOKP Milestone 6 then...
Again there came to be a day when my phone started switching off as soon as it started within 10 seconds..
I had my Airplane Mode ON 'cause I was in my class and when I turned on bluetooth, my phone went mad.
In those 10 secs for which the phone was on, it was laggy, just preparing to shut down.
I saw that bluetooth was turned off when I pull the notfication bar down. Tried to turn it on, asuming it would solve the problem, but all in vain.
Then it was really important for me to call home due to some reason.
When I tried to turn off the Airplane Mode, the phone immediately got switched off again.
Then I did this :
1. Opened the dialer app.
2. Typed *#*#4636#*#*
3. The 'Testing' menu appeared.
4. Tapped on the 'Phone Information' option. (10 secs were about to get over)
5. Scrolled down and pressed 'Turn on radio' button.
6. BOOM! The phone didn't switch off again! -The Airplane Mode was still on, BUT I was connected to my EDGE Network and could also access the internet!
Then I could call / use the mobile for a while till I reached home.. I made a backup of several things on my phone using JS Backup.. Didn't dare to mess with the airplane or bluetooth buttons them.. Then changed the ROM when I reached home.

Oops..
Ohh .. Sorry moderators..! I think I started this thread in the wrong section.. Someone please move it to the 'One V Q&A, Help & Troubleshooting' section.

I'm not a CM9 user but congrats that you've found out a workaround for it. Something smels fishy in your problem cause no one reported this kind of behavior before and I am 100% sure that maxwen's work on both bluetooth and cm9 was flawless.

1ceb0x said:
I am 100% sure that maxwen's work on both bluetooth and cm9 was flawless.
Click to expand...
Click to collapse
Umm.. what do you mean by that? Is the Bluetooth problem fixed....? I'm on CM10 now just because of the BT Prob in CM9..
Sent from my One V using xda app-developers app

i mean that the problem is at your end1

Yea I never had a problem check kernel....
Sent from my One V using xda premium

cybervibin said:
Yea I never had a problem check kernel...
Click to expand...
Click to collapse
It really happened to me three times using 201212251747 HELLBOY Kernel.. Is the problem fixed now? It won't happen if you use Bluetooth occasionally.. I use it everyday and it always happened within 6-7 days. Them I had to again reflash the same or change the ROM..
Sent from my One V using xda app-developers app

Paresh Kalinani said:
It really happened to me three times using 201212251747 HELLBOY Kernel.. Is the problem fixed now? It won't happen if you use Bluetooth occasionally.. I use it everyday and it always happened within 6-7 days. Them I had to again reflash the same or change the ROM..
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I'll check if ur using the proper kernel once I reach home...yea I use it in the car for music and sending images and stuff
Sent from my One V using xda premium

cybervibin said:
I'll check if ur using the proper kernel once I reach home...
Click to expand...
Click to collapse
Thanks I'll not even waste a single second in turning to CM9!
Sent from my One V