Related
The S2A dialer used by most chefs in WM6.5 ROMs has a major problem. If the phone is in standby, and a call is received, the phone cannot be answered, either with the slider or with the hardware button. I have experienced this with both Shep's ROMs and EnergyROM 3.0 with 100% consistency, and have had to call people back almost every time I receive a call.
I've seen several posts here and elsewhere about others experiencing this as well. In fact, in relation to the posts here... for some reason, the moderators determine that the problem is not "ROM-related" and that the threads should be frozen or deleted, or moved to specific ROM threads. I don't think that this is the best way to handle this, especially considering that nearly all chefs are using this dialer and none seem to mention this common issue in their release notes. This is not ROM-specific! It is a problem with the S2A dialer used by nearly all chefs alongside WM6.5.
Currently the only workaround I can find is to hit the power button twice before attempting to answer the call (since the call itself doesn't seem to completely wake the phone up), or to skip S2A altogether and use the Windows dialer.
Yes, i noticed this too, only for my phone it seems to take a bit more time to wake up (so it is possible to answer). I'd use the MS dialer, only I hate the look of it when phone is on and i receive a call... It only shows a notification or something... Maybe somebody can find a registry tweak or something.
I have tried Shep's rom and currently using NRG's rom. I have not had this issues with either. I have not seen others have this problem posted in their respective thread, which is probably why this is not something they would post as known problem. The only well known issue that happens regularly is the notification showing up along side S2A, but that interfere with the ability to pick up phone calls. If you believe it is a rom issue, try posting it in the respective thread.
Just a reminder, ALWAYS perform a hard reset after you install a new rom, that very often corrects a non regular occurring issue.
AndyJ91, Currently there is no fix because HTC S2A was made for 6.1 and not 6.5, which is why until HTC makes a fix or release a new version for 6.5, there is really nothing much the chefs can do.
Not sure I understand the issue. I am using Energy 60109. I can answer calls when the phone has been idle for hours. Perhaps you should define "Standby". By that do you mean that you briefly press the power button to turn the display off? Or is there more to "Standby"?
If that is the case, it works fine for me every time. Maybe you have some other program that is causing problems. Try a hard reset and test it before you make any customizations or load any software. Sort of a "factory fresh" test.
Doug M.
i didn't notice this problem either when i was running NRG 3....noticed other problems so i switched back to 2, but the S2A was working fine. YOu could always lengthen the ring time on your calls so you don't miss them..
I also experience the same problem . . . The phone rings . . . I slide to answer . . . I say, "hello . . . hello . . . anyone there? . . . hello . . ." for the next 15 seconds. Occassionally, I'll actually connect to whoever has called. Most of the time they are sent to voicemail and I have to redial them.
I'm at the point where I want to chuck my phone down a sewer because of S2A. Is there a way to disable it? I'm using EnergyROM 3.0, 6/01/09 version.
AUTiger83 said:
I also experience the same problem . . . The phone rings . . . I slide to answer . . . I say, "hello . . . hello . . . anyone there? . . . hello . . ." for the next 15 seconds. Occassionally, I'll actually connect to whoever has called. Most of the time they are sent to voicemail and I have to redial them.
I'm at the point where I want to chuck my phone down a sewer because of S2A. Is there a way to disable it? I'm using EnergyROM 3.0, 6/01/09 version.
Click to expand...
Click to collapse
You can always disable the dialer and use the MS dialer, but the keys are so tiny it is difficult to use ...unless you put your finger in the pencil sharpener.
A less painful solution may be to simply install another dialer on top of the current one. Search for the Diamond Dialer of the original ATT dialer and try one of those.
If you can't find it, send me a PM with your email and I'll send it to you tomorrow when I get back to the office.
Doug M.
This issue has been discussed at length in other threads.
The default HTC dialer is incompatible with the wm6.5 lock screen, leading to issues including the send and end keys being unresponsive.
To disable the HTC dialer use Advanced Config, first option under phone section. This will restore the ms dialer which works just fine.
If you dont like the stock dialer some people have had success with 3rd party ones, but bear in mind that these have not been designed for 6.5 either, so you may see other issues.
I had this same problem on 6.1 with NATF and Arrup's ROMs.
Have you tried . . .
. . . THIS dialer?
Its from the Tachi, which came with a 6.5 ROM. I honestly don't know how well it works from Standby, but it couldn't hurt to try, I'm sure.
tachi dialer
Captain_Throwback said:
. . . THIS dialer?
Its from the Tachi, which came with a 6.5 ROM. I honestly don't know how well it works from Standby, but it couldn't hurt to try, I'm sure.
Click to expand...
Click to collapse
The tachi dialer works well while in standby, somehow it unlocks the phone first..then you use the S2A. Give a try. I use EnergyROM as well.
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 been trying to set up a VoIP client on my Windows Mobile phone for a long time, starting with the HTC Wizard which I could never get to work.
I have finally managed to get a VoIP client with a really nice interface working on several phones that I have tried it on.
I am using ViaTalk as my provider but it should work with any VoIP provider.
It works great (with a slight delay, nothing that I can't live with) on an unlocked HTC Sprint Touch Pro 2, a T-Mobile HD2, a HTC Diamond and an HTC Fuze.
The application is by NCH software out of Australia and it is free to use, or if you want to unlock all of the features of the application, download and register the business edition.
Here is the URL for the download:
http://www.nch.com.au/talk/pocket.html
Or if you would like, PM me and I will be happy to send it to you as an attachment to an email.
Only known issue is when the phone goes in to power saver mode it drops the WiFi connection but that should be an easy fix, right now I am simply pressing the power button and it comes right back and the connection is still alive.
wow men! you are amazing! you search better than me xD you have a paid version? or free version?
hecthork said:
wow men! you are amazing! you search better than me xD you have a paid version? or free version?
Click to expand...
Click to collapse
I am using the paid version but the only difference is that it unlocks some additional features that most people proably don't need anyway.
It is not trialware so it has no expiration.
thx you man, i'm trying this app since yesterday; works good!! easy to configurate, i'm using the free version because; i don't have 2 line, i don't use conferente mode... but it will be interesting trying these features xD
How does this app compare to AgePhone?
Hello,
why not to give a try to PortGo !
http://www.portsip.com/softphone.htm
The free version is sufficient and very simple to use, even with several providers (I currently use 2). Skin and language are easy to adapt if necessary (I've made it for French), see also here http://forum.xda-developers.com/showthread.php?t=508715
Dangze
bobzero said:
How does this app compare to AgePhone?
Click to expand...
Click to collapse
I really couldn't tell because I have never tried AgePhone.
I have tried most of the different VoIP clients mentioned throughout this site but I have never been able to get one to work right until I tried this one.
It could be that I am too stupid to configure them right or it could also be that they simply don't work very well, I can't say.
As for PortSIP, I never got it to work right and the developer dropped off line a while back as far as I can remember.
This little VoIP client that I am using has got a clean interphase, it is easy to configure, it does not require any special "helper" apps. so I am happy with it.
Hope that some of you enjoy it too.
I sincerely don't know the use of that softphone over the built-in VoIP for WinMo (WM65VoIP.cab, ultimate.VOIP.WM6.5.cab - available in several threads here) - except you need 2 lines? Especially as these guys do not use the WinMo address book! I don't want to manually add 600 adresses to any additional phone book.
The above mentioned cabs integrate into WinMo and use WiFi or 3G-connections. The phone rings as ususal and displays who called (from WinMo address book). The call is even entered into WinMo callog (only disadvantage: You don't see if a call was made/received via GSm or VoIP). I use them on my TP2 (WinMo 6.1), HD2 (WinMo 6.5.5) and even had a cab file for HTC Artemis (WinMo 5). All works/worked pretty well
So what's the use of these softphones?
Cheers, Franky
ardec1 said:
{R^7Z trim]
Only known issue is when the phone goes in to power saver mode it drops the WiFi connection but that should be an easy fix, right now I am simply pressing the power button and it comes right back and the connection is still alive.
Click to expand...
Click to collapse
I have mine set so that the light always stays on until I turn it off(I turn off auto back-light, my preference). So, no issues there. Additionally, I think there is a setting or app that will allow WiFi to run even while the phone sleeps. Or perhaps it is set into a low-power mode until the power key is pressed?
Howto in France ?
It seems great but how could I make it work in France.
My provider (mobile or at home) is SFR.
Thanks in advance to all for your answers.
Setup file attached to original post
I finally got around to attaching the setup file to my original post so it can now be downloaded directly from this site
Hi,
I suggest to please change the title to "Express Talk for WM".
I already tested it on my Ultimate 8502. I can call but can not receive incoming call. It ring but after receiving, it stop ringing with no active call and no sound. Any solution?
thanks
sadat007
After installing Pocket Talk and configuring it I get the message that my handheld device is blocking UDP port no 8000 and 5060. Of course it isn't but I can't make callas. Has anyone had the same problem?
installation unsuccessful
It fails to install for me...
I connect my HTC Mega (Windows Mobile 6.5, moded rom), I start the setup, my phones screen shows the installer but than says "Installation of NCH Swift Sound Pocket Talk.CAB was unsuccessful"
Doesnt matter if I choose MainMemory of StorageCard.. there is plenty of free space on both of them.
Any Ideas? Are there any prerequisites? I checked the NCH forum but couldnt find any help...
PS: trying to install directly from the .cab it leaves on my storage card wont work either
Hi sorry for my bad english, setup doesn't work on my hd2 why???
Franky24 said:
I sincerely don't know the use of that softphone over the built-in VoIP for WinMo (WM65VoIP.cab, ultimate.VOIP.WM6.5.cab - available in several threads here) - except you need 2 lines? Especially as these guys do not use the WinMo address book! I don't want to manually add 600 adresses to any additional phone book.
The above mentioned cabs integrate into WinMo and use WiFi or 3G-connections. The phone rings as ususal and displays who called (from WinMo address book). The call is even entered into WinMo callog (only disadvantage: You don't see if a call was made/received via GSm or VoIP). I use them on my TP2 (WinMo 6.1), HD2 (WinMo 6.5.5) and even had a cab file for HTC Artemis (WinMo 5). All works/worked pretty well
So what's the use of these softphones?
Cheers, Franky
Click to expand...
Click to collapse
Myself some hours ago said:
I'm also using WMVoIP and my phone is enabled by default to use VoIP when wi-fi gets enough data traffic, so I don't need other VoIP apps except for second lined. Usually I switched off the phone radio and whitched on the wifi radio and VoIP wasd enabled as default phone line.
But my problem is now I can use VoIP over 3G at no penalization from my phone provider, and I can't set my phone to use VoIP by default.
Is there a way to set VoIP the first option and phone the second one, using 3G (not wifi) ?
Click to expand...
Click to collapse
Editing: I found this xda-dev's app here: http://forum.xda-developers.com/showthread.php?t=730303 and it works fine with one SIP line, in my Kaiser, even using 3G instead of wifi.
Thanks !
It works fine on my HTC Touch Pro cdma with wm6.1.
But I don't like the fact I can't use my original contact list...
Hey Guys,
Im wondering what would be better for me, Im based in the UK and I want to know if Using a VoIP Service such as Skype or get a Dedicated Phone line put into my address? what do you guys think?
- David Scheme
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Ive got an unlocked Atrix too and now in Germany, I have the same problem. Motorola should definitely look into this.
Here's a quick fix for it thou, (not permanent)....
1. type *#*#4636#*#* on the dialer
2. Chose Phone Information
3. Set preferred network to GSM only
Viola...its fixed
problem with this fix is that you wont be able to use your 3G network but the dialer should be working.
Thanks Nazrin (for both replies) !!
It sure did the trick, though no data access is not acceptable on a phone like this!!!
So this meens that all unlocked Atrix's in european GSM networks have the same problems? Haven't seen any others reporting this and there are quite a few in use I've noted in other forums.
Was thinking of trying to have mine replaced (which probably won't be easy and take long time...) but that won't change anything then??
We have to wait for the european version of Atrix rom I suppose??
Any others with the same problem??
No problems buddy, glad it worked..and i have to agree with you..this bug is unacceptable...it seems the phone just ***** up everytime it calls on utms (3g)...im sure there is more people with this problem...
Sent from my Supercharged MOTO ATX
I have the same problem
Hi guys, I have the same exact issue (I'm also in Belgium, on Mobistar). I'm somewhat glad to hear this is a generic issue, and not an issue with my specific phone. At least I can be fairly certain replacing it won't solve this issue then.
I made another post here before I came across this one, has a bit more info: we are seeing modem panics when using 3G + outbound call. I've also contacted Motorola support to no avail:
http://forum.xda-developers.com/showthread.php?t=1028771
You can also read there that I tried another operator, and it did not crash with that one (although 3G did disconnect).
Hopefully Motorola/Qualcomm will start to notice the bug when they release the phone globally, and release a fix.
Either that, or we all have phones from the same bad batch
This bug is really bad for users in europe....cant call on utms...
I really hope motorola takes this seriously cos if there's no fix via software updates then its moto gone for me
Guys, you are all on unlocked att atrix right? I do believe it is a simmiliar software glitch/bug/lock that you have porblems using it on non att networks as the problem with the wifi that it stops working for some of us (check the thread about it for more info). As all suggests there it is a config file problem, unfortunately i or anyone else doesnt know yet which one....
Yeah maybe..but funny thing is wifi is working without a glitch...will have to read that forum later...
Workaround options
So, since it seems we're not gonna get this fixed until there is a new radio/modem firmware available for flashing (and even then..), I've been looking for a workaround.
Found two potential applications that could do what we need: disable data completely when making an outgoing call, or switch to 2G:
- Sanity
- Superpower
I've tested the first (Sanity), and it does not work (fully). It does seem to disable data, but the bands aren't switched so our problem remains. I've contacted the developer here: http://tagliamonte.net/forum/thread-10.html. He seems to be very responsive, so given enough interest, I think he would add the functionality we require.
The second app I only came across today, and have not tried yet. It does not have a function to specifically switch bands when making an outgoing call, but it has a trigger for "Foreground application", so if we make that the dialer/contacts... Question remains if it will be able to do the switch.
Hopefully one of these will lead to a decent workaround for all of us!
Well done unknown...i will try these apps... but the real fix should be from moto...im always reading the net for anything that can solve this issue
reboots on incoming and outgoing calls
Same in Russia on Megafon network, I had to enter 4636 menu and use it as "GSM only". Even this does not fully solve problems, e.g. call forwarding does not show the new destination number while it does actually make the phone divert calls correctly.
My hope is that UK release will trigger new software version which will address this issue. ANYONE has news on this?
FIXED!
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
_unknown said:
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
Click to expand...
Click to collapse
Worked for me as well..brilliant!!!! its working here in germany.....but I wonder the telstra radio will work in my home country with frequencies of 900/2100
Motorola Atrix restart when placing a call
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
No answer
Why I never got an answer of any post I did?
There is something wrong?
Eli
elijacob said:
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
Click to expand...
Click to collapse
Forget about those ways
klingsurf said:
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Click to expand...
Click to collapse
[Sorry for problem in speaking]
i had that problem too , im using CM13 with Marshmallow Version of android
So . the easy way is :
***** search "Default" in settings. then choose " System dialer" as Default ! just it ****
but if there is no search bar in your setting . try this patch:
Android 6 : Setting/Apps then click the setting icon on top(may be diffrent in your case) , then Click on "default ...." then choose " System dialer" as Default! :fingers-crossed:
but in some cases that it didnt work . they have to reinstall gapps .
Or in official Roms , reset will be usefull
any quastions?
Hello,
I have the asus zenfone 9 , I bought this phone only because it had the native call recording service , this service is absolutely necessary for my work.
Unfortunately, after a few days it automatically upgraded to android 12 and this important feature was lost.
I installed dozens of apps, wasted a lot of time, has read hundreds of articles on forums and nothing has worked like tha native call recording service.
I decided to proceed with the root & unlock of my phone, with the unique purpose of getting the mobile phone to record again.
Can you help me>?
do you think this is a good idea?
Hi Nico.
The Zenfone 9 comes with Android 12 by default, it has never had 11 commercially.
Now you've unlocked your phone, when you don't need to. And maybe you've lost your warranty, because tech support is there to solve these problems, even on the phone.
We forget that when we buy a phone, the technical service is there to help us, that is what we have paid for it.
And now I belong to the Android 13 beta program and calls are still being recorded.
Maybe it can serve you to Truecaller.
on A13 zenfone 9 records calls very well. A12 also no problems
Same here, record option is present and works very well (Android 12 et and after the update to Android 13)
Do you use the native Asus contacts & calling app or did you install another app ? (if you did that then yes the call recording option is not present you must revert to the native call app)
The call recording function can be missing depending on your location (its illegal in some countries). Thats why its on some CSCs only for samsung phones.
My guess is that it was enabled for the firmware in the country your phone came from, and when it detected a different country for the update, it changed the locale of the device and removed the call recording function.
I don't see different locales for the firmware posted in https://www.asus.com/mobile/phones/zenfone/zenfone-9/helpdesk_bios/?model2Name=Zenfone-9 it says "WW/EU/RU/IN/TW" so pretty much the whole world.
Maybe the country spectific restrictions get in effect after the first time setup? Try removing the sim card, flash the firmware from Asus website above, do a complete factory reset and don't put the sim card or connect to wifi during the first setup, until you see the home screen.