Related
In LG Optimus One endcall function does not work, so do not work correctly call blocker apps. Can this be fixed in a custom ROM?
telephonyService.endCall() function BUG
Hi everyone!
I confirm that there is a bug with telephonyService.endCall() function which consist in passing call to this function to nowhere, thus making ALL call blocking software useless, because they can't discard unwanted calls.
Can anyone fix this problem? I believe in you, GURU, take a look on this problem please.
With respect and hope, Max.
I really think this topic deserves a bump. And a solution.
Same problem here. End call function simply doesn't do anything on this phone making call blockers completely useless. I tried all O1 roms and even the original rom with the latest update and still doesn't work. Every call blocker says that call was blocked while you are watching it ringing.
By the way until someone comes with a fix, i found a temporary solution which requires Tasker or Settings Profile application.
If you want to send the blocked number to the voicemail, simply program Tasker to switch to airplane mode on and off or if you want to do the pick up and hang up action program Tasker to accept the call first then switch to airplane mode on and off.
As you can tell it will disconnect you from your network temporarily but Tasker is quite fast doing it so you will be on again very quickly. Putting your phone into airplane mode will end the call very quickly which call blockers can't do for this phone right now. You can do all these with Settings Profile too with the same steps.
Until a software fix, any other ideas are more than welcome.
(Unknown and private number value for Tasker is 0).
I have had the same problem and confirmed with Tasker developer that this is bug in LG Optimus One. Airplane mode is good solution if you do not protect your sim card with pin code. Else, after airplane mode is switched on and off, you will be prompted to insert pin and until you do so, your phone will not be reachable
I would prefer different solution...
I think we need to ask the guru to fix this problem. I said two weeks ago with mik_os about this issue, he replied that he might look, if not occupied by another.
Bump
This is something that is important as we cannot handle unknown calls.
If anybody has some solution, it would be appreciated.
I'm working on that.
For now I'd found by debugging phone with adb that endcall function really do something, but it seems that at the wrong time:
[ 02-16 20:27:52.451 1589:0x635 D/PhoneInterfaceManager ]
[PhoneIntfMgr] CMD_END_CALL: no call to hang up
Click to expand...
Click to collapse
That message appeared two seconds after we got the call (it's a mystery what phone was doing during those 2 secs), but before the framework starts to search corresponding contact to the calling number.
May be we have to wait several seconds after we get the call to invoke the encall() function again?
I'm a starter with android and I have not so much time for that, but I'm now trying to write a little program that will invoke endcall() function any time a want to prove/disprove my theory.
If anyone had written such program already, you can share sources with me to let me test that condition, or try it yourself.
UPDATE:
I've just tested it: there is no matter when you invoke endcall() function, the result is the same "[PhoneIntfMgr] CMD_END_CALL: no call to hang up". So digging deeper.
Last information from Android sources (how it should be in Android and doesn't work on our phone):
method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java
Digging deeper...
First of all, that's environment I have:
- LGP500 device )
- "void" custom firmware
As I mentioned before, method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java.
To check what's wrong I tracked that method to Phone.apk in /system/app/ directory of "void" custom firmware, which was grabbed from original LGP500 2.2 firmware, unpacked it and dedexed classes.dex file from it. To my great surprise I've found that it really omits call to hangup method of PhoneUtils class and do many things, that doesn't cross with Android sources. So LG programmers did their own "Android" with their own bugs. I have to say that it omits call to hangup method only for GSM call, but it has to be done for CDMA calls well.
I'll try to build Phone.apk from Android sources. This may take a while (maybe a week or so). Or maybe I'll edit dex file and repack Phone.apk with a new one. We'll see when I finally get some sleep
FYI, there is another way to block calls by diverting some call numbers to voice-mail. This is built-in Android function. That could be done in your phonebook by selecting a contact, pressing menu button, selecting options and checking "Incoming calls, Send calls directly to voicemail" checkbox. This way works more quickly than any other methods, used in callblocker software. So blocked caller immediately hear busy tone. I'll dig in sources how it works and maybe will find a better way for callblocking software.
Sorry for my English.
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
vault1965 said:
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Of course I need help. What kind of help can you offer? Do you know how to build Android on Ubuntu 10.10? I've read couple of articles about that, but still it would be great if somebody familiar with that can join that topic. I'm familiar with linux only in network services administration and a little with programming in couple of languages.
BTW, I've found another bug in our LG firmware - Skype (and another one program, that I can't remember name of) can't switch sound to speaker. Instead it always playing sound (I mean voice of person you're talking with) through loud speaker. And again I think the problem is somewhere in standard *.apk files, which are Android framework.
Had anybody tried gingerbread?
Had anybody tried gingerbread from that topic http://forum.xda-developers.com/showthread.php?t=909242 ? Does it solve the problem? I'm currently reading that topic when I have time (there are a lot of words not in my native language) to decide whether it worth to be deployed on my device. Because of that currently I had stopped further investigation to solve the problem on froyo.
If anybody has some experience with that gingerbread build, let us know please.
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
vault1965 said:
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
Click to expand...
Click to collapse
Hardware EndCall works on our froyo with key remap also. I was asking is it API "endcall" function working (you can test it with simple "CallFilter" program from the market)?
BTW, that API works fine on Nexus One recently upgraded to gingerbread. So information about removing call api's is a fake. Also I can refute that information as I saw this API's in gingerbread sources with my own eyes.
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
cigman said:
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
Click to expand...
Click to collapse
Thanks for information.
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Sent from my LG-P500 using XDA App
migueel said:
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Click to expand...
Click to collapse
Try Gingerbread at http://forum.xda-developers.com/showthread.php?t=909242
It has to solve the problem
i have the galaxy for 5 monthes now..
switched tons or ROMs and kernels.
since i tried the 2.3.5 androidmeda(i think it started there) i have a problem answering my phone.
when someone call me i can slide it right in order to answer, the phone stop the ringtone like i answered but i cant hear anything hile the other side think someone answered him as he doesn't hear the tome anymore.
i tried to go back to KG5 but i cant get rid of it.
it got better as i changed the modem(used to be on KI4) to KE4 and KG5(the rom im with right now but its not good.i can answer but it takes 5-10 seconds before i see the call screen and able to talk properly.
tryied androidmeda,cognition,batista,xpower(the used to be),villain and so. none helped so i guess its not ROM related exactly.
Maybe some data was changed (such as the opening after trying androidmeda-the white turning cube and the android character insted of the samsung s 2 pic).
i tried various MODEMS in order to solve it but no progress yet.
anyone familiar with this problem?anyway to solve it?
Sounds like a hardware problem more than a rom problem. You have tried all them custom roms do its quite odd. Id say trying to go back to a full stock rom if you haddent already and maybe test out other voice features on the phone like voice record and the google voice search thing.
Sent from my GT-I9100 using XDA App
Hi guys. I have a peculiar problem in my new Galaxy S3. Whenever I make a call, the screen remains on even though I have ticked the 'Auto screen off during calls' option in call settings. Also, whenever I input any numbers while in a call, the keypad does not hide. I mean I get the 'Hide' option but it doesn't do anything and the keypad stays on the display. Can anyone tell me if this is a known issue or am I the only one facing it? Is there any workaround this? I am on stock firmware (XXLF2) and haven't even rooted my phone yet. Please help me guys!
I have exactly the same problem. I know the proximity sensor works, because I tried the proximity sensor test app. But my phone does not turn off screen when in call.
i have same problem any one help us ?
I also have this problem.. and to make it worse, I can't seem to call out occasionally. I swipe to call, but nothing happens. I can't even dial out at times.. rebooting usually solves the issue, but the problem quickly comes back.
I'm not rooted, on stock rom. Anyone know what the issue is?
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
BlueG2 said:
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
Click to expand...
Click to collapse
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Beards said:
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Click to expand...
Click to collapse
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
BlueG2 said:
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
Click to expand...
Click to collapse
'Voice' was my search pattern. It's got to be there I'll find it.
Hi guys,
Did you find a solution to this problem yet? I have the same problem, and no matter what I do, I can not make it work. The screen is always on during a call. I am using the stock rom, without root, as it is.
------------
Nevermind. I fixed it by removing FSC ID, apparently it was interfering.
i had the same problem but it was fixed after i made a phone restart.
I have the same problem...
Hi.
I was using my Atrix with CM7 MROM for long time.
Yesterday I switched to CM9 Olympus with new kernel by krystianp. It's great rom but...
I got two little problems:
1. when I plug my headset I don't have icon informing about this.
2. when headset is plugged it auto pick up calls. I found something like this "phone>menu key>call settings>Accessory settings for call" but I don't have this options in my dialer or anywhere else.
Can anyone help me with this? Icon is just a feature I liked but auto answering calls is a little disturbing for me. Especially when I don't know who is/was calling.
It is pretty clear you don't know what you're doing, or else you wouldn't flash an experimental ROM and then complain about a bunch of already very well known issues.
I suggest in the future you stick to GB ROMs and stay away from things you don't understand.
ravilov said:
It is pretty clear you don't know what you're doing, or else you wouldn't flash an experimental ROM and then complain about a bunch of already very well known issues.
I suggest in the future you stick to GB ROMs and stay away from things you don't understand.
Click to expand...
Click to collapse
I thought auto answer was normal function which is working and I didn't find anything about problems with it. So if it can be turn on should also be able too turn off...
I know that new kernel and roms are in development and that they have some bugs (proximity sensor, screen tearing, problem with some games) but one app which I needed runs only on 4+ Android.
So could answer me it is possible to turn off auto answering calls or it is bug which I miss reading threads about kernel/cm9/cm10?
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
m4ckys said:
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
Click to expand...
Click to collapse
please read how to get answer quickly in my signature
and provide logcat just after the error occurs
this will help
m4ckys said:
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
Click to expand...
Click to collapse
First of all, JellyBlast is a banned rom here. So lets not have anymore discussion on that. As for the headset problem, you can use the SoundAbout app from Google Play. Do post the result. Hope I Helped
Thanks for the replies guys. I will have a go at the catlog later when I get home and post the results.
The problem doesn't happen every time so hear with me while I try to get it to do it so I can post the log.
Sorry for mentioning 'that' rom, I was just using that as a point of reference as it was the only rom I have tried.
The headset issue isn't that the headphones don't work though, it is that using the Bluetooth headset causes the phone to crash when answering a call (not making one though), and I thought that using the sounds out app was to fix the headphone socket issue?