Related
Dear all,
I'm a new member here also It's my first experience using an android phone.
Lets get into my problem.
It's related with my hero's bluetooth function. I have tried to pair and connect with many phone starting with BB Bold, Nokia e51, Samsung star. The problem is same that my phone can be paired with those phone but it was failed to connect with them.
Please help me for the hero's lovers here, what must I do / any suggestion?
My phone information:
Firmware Vers.: 1.5
Software Vers: 1.0.0.A6288
Sorry to inform you that the Bluetooth function on the Hero is only for connecting to a headset, at this present time you cannot pair, send or receive files with out and app from the market. Even then to receive you have to be rooted and then the apps don't actually work on the Hero perfectly as of yet. HTC may fix this but I don't think it will be very high on the priority list of to do's!
Ohh mine.. It's too bad to know the fact. I think it will be almost completed features if HTC develops more this feature.
@seanyowl --> many thanks for your information.
I would like to confirm my understanding based on your explanation as following:
1. For now, the function of blue-tooth in HTC can not for pair or even receiving file. It just for connecting to a headset, not with other phones. Is it right?
2. If i want to receive or send files through this feature, I should have an apps which supports this function, is that right? So what is the name of apps?
3. What is the meaning of this statement "Even then to receive you have to be rooted"?
I'm sorry asking this question since it's my first time using android phone and smartphone. It's a big jump for me from my old phone (siemens ME 45)
Many thanks for help and support for me in this thread.
Bluetooth and Root
1. Yes
2. Yes
As for 3 see posts:
http://forum.xda-developers.com/showthread.php?t=552591
http://forum.xda-developers.com/showthread.php?t=543571
Nice response
Bro.. many thanks for your help..
I do appreciate it. Cheers and have a gud day.
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
Hey guys, I upgraded to the Atrix from my Tilt2... I set up the bluetooth with my car (Audi A5) and the calling works fine but the car no loner imports my SIM contacts, recent calls, missed calls, and dialed calls list that my Tilt2 used to send over. Those options on the car are now just blank. Is there anyway to enable this? The bluetooth profile on both phones is just listed as "hands free". Is there any way to fix this or enable other connection profiles to send that data like my last phone did?
Thanks guys
I can pair my Atrix is my BMW 3-series but when it tries to download the phone book the BT connection drops. Sometimes I can start to make a call but it will drop the connection.
I can connect all my BB's and my HTC Inspire 4G just fine.
I think there is something wrong with the BT stack.
Ziuck said:
I can pair my Atrix is my BMW 3-series but when it tries to download the phone book the BT connection drops. Sometimes I can start to make a call but it will drop the connection.
I can connect all my BB's and my HTC Inspire 4G just fine.
I think there is something wrong with the BT stack.
Click to expand...
Click to collapse
I think you may be right... I did some more online searching after the post and stumbled upon an Audi forum where multiple people have lost the ability on several different car models after moving to a stock android device... however, it appears things fix themselves with CM roms which may have a more sophisticated BT stack. I wonder if it's hopeless about having that capability until 2.3 or the bootloader is cracked?
If I can't get this fixed soon then I will be forced to return this phone.
How can they screw up something so simple??
UTZorro said:
Hey guys, I upgraded to the Atrix from my Tilt2... I set up the bluetooth with my car (Audi A5) and the calling works fine but the car no loner imports my SIM contacts, recent calls, missed calls, and dialed calls list that my Tilt2 used to send over. Those options on the car are now just blank. Is there anyway to enable this? The bluetooth profile on both phones is just listed as "hands free". Is there any way to fix this or enable other connection profiles to send that data like my last phone did?
Thanks guys
Click to expand...
Click to collapse
I have this same problem in my Chevy Volt. Sometimes the phonebook works (but very slowly) but the call lists never work. Also seems to take a very long time to pair initially.
Sent from my MB860 using XDA App
A lot of cars can only import the phone book from the SIM card. Not from any other application on the phone.
So if your phone book is in Google Contacts or some other application...you'll need to port it into the SIM card itself for most cars to be able to read it.
Return it. I have new A4 and atrix pairs fine. I actually think its the clearest device I've used in my car yet
Sent from my MB860 using XDA App
fade?
"I have new A4 and atrix pairs fine."
And do you know WHICH phone book your numbers are in, or which phone books the A4 can pair with?
If his BT is connecting, and the phone is working over BT, there's no reason to think the phone is defective. yet.
UTZorro said:
I think you may be right... I did some more online searching after the post and stumbled upon an Audi forum where multiple people have lost the ability on several different car models after moving to a stock android device... however, it appears things fix themselves with CM roms which may have a more sophisticated BT stack. I wonder if it's hopeless about having that capability until 2.3 or the bootloader is cracked?
Click to expand...
Click to collapse
It's not a BT Stack problem...it's an Audi problem (or BMW, etc...). The manufacturers need to program their devices for Android. The ability to grab contacts and such isn't a standard bluetooth handsfree device option. It has to do something extra. How it *handles* that extra something differs by device...which is why some don't work with Android devices.
On top of that, there's a dialogue when you first pair the device that asks if it should have access to your contacts, call lists, etc...that you have to "Allow" or it won't ever be able to get those lists. It's been the same way on every Android phone I've ever used. If you don't hit Allow within 10 seconds the dialogue will go away and never come back...unless you unpair and re-pair the device. Try doing this and seeing if the dialogue comes up. If it doesn't, it's an issue with the way your Audi/BMW polls for contacts.
BTW works perfectly with my Kenwood receiver.
Ziuck said:
If I can't get this fixed soon then I will be forced to return this phone.
How can they screw up something so simple??
Click to expand...
Click to collapse
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
hotleadsingerguy said:
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
Click to expand...
Click to collapse
I have the 08' audi a4 and my contacts sync just fine, as do the missed calls.
" my contacts sync just fine"
SIM card contacts? Google Contacts? Exactly which or what "contacts" ?
Hi, new user here to searched and figured it'd be better to post in this thread rather than starting a new one.
I'm another Atrix user who is having issues with pairing the Atrix to a bluetooth car kit. I've got the VW Touch Phone Kit (rebadged Bury CC9060) which used to work perfectly with my previous Samsung Omnia as well as my partner's Samsung S8500. The problem I have was that with the 1.57 firmware, I could initially pair the phone and it would sync the phonebook up fine so that I could make or receive any number of calls without a hitch. But the issue was when I switched the ignition off then back on, the Atrix appears to pair correctly, it'll grab the phonebook but cannot make or grab any incoming calls. When dialing from the phonebook, it will initiate the call then drop out while the call still goes through. Incoming calls just aren't picked up at all. If I deleted the pairing and paired the phone up to the car kit again, it'd work until the first ignition off and back on again.
After I updated to the 1.83 firmware, this no longer works for me at all even though it appears to pair correctly and syncs the phonebook as well.
I've looked into upgrading the software on the car kit but I'm already on v0181 which is the latest for the VW branded kit. The Bury CC9060 kit has available a v0235 update but won't load on the VW kit as it does a checksum check. I'm looking at possibly editing the flasher to bypass the checksum check.
Has anyone else used the Atrix with this car kit and experiencing the same issues?
Thanks in advance
fmflex
A quick bump.
I find it hard to believe that I'm the only one using an Atrix with this car kit...
I really wanted to buy a car kit, I was even willing to pay the rather high price. Then i saw tht the Atrix just "snaps it" with those two spring arms.
You know what happens in an accident? The phone will fly out as a missle. Good luck finding it, if you were doing 30 when you got slammed, the phone will still be doing 30 when it launches out of the clips.
If it doesn't hit you, you still won't be able to find it or call 911 on it.
So, nice dock, I'm holding off for something that can be used "in case of accident". For that price, I expect a more robust product, designed to survive. (Note to Moto, calls Mercedes and speak to crash safety team.)
hotleadsingerguy said:
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
Click to expand...
Click to collapse
I am not sure that the blame can be directed to the car makers not suiting the android configuration.
I had concerns about Androids paring car bluetooth, so when my wife got her Samsung running Froyo before i purchased the Atrix, I tested it on my 2010 A4 and it all worked faultlessly. All phonebook, dialled, missed calls & received calls. All her contacts are stored on the Phone too, not the SIM. It actually worked better with it than my old Nokia's, and my old iPhone 3G. All of which had contacts stored on the phone not the SIM.
Being in my car all day, I had to make sure it the Atrix running Froyo would work too, and that's why I tested it with my wifes phone before buying the Atrix.
I would have to say that the problem does have something to do with how the Atrix handles bluetooth. I have been having all the same issues that other users are having.
To be fair to the Atrix, I had only one problem when I originanlly bought it and that was loading the contacts from the phones storage, all the other options were working and it never displayed the annoying error message and it never dropped the connection either.
This has only started playing up completely since I rooted it and installed HeLauncher with Fancy widgets (maybe it's just a coincidence, but its unlikely i think IMHO).
I have since uninstalled the HeLauncher and Fancy Widgets, and yet the problem is still there, so I have no realistic reason why it isn't working anymore.
Because i work for Audi, I will check at work why this issue might be happening ( just with the Atrix not all the other Android phones) and see if their is anything that can be done to fix the issue.
Hi Staunch
I'd be very interested in what you can find out about this issue. I've basically got nothing out of VW and their official stand is that the atrix isn't compatible.
fmflex said:
Hi Staunch
I'd be very interested in what you can find out about this issue. I've basically got nothing out of VW and their official stand is that the atrix isn't compatible.
Click to expand...
Click to collapse
Ok, I have tried connectivity with the current version of MMI and it seems to pair up with NO error messages at all. It would appear at this stage that the new MMI generation have the "issue" fixed. I am still waiting for a reply from Service Technical Support to answer why the issue exists on the older MMI generations. It would appear that Audi in conjection with Apple focused their MMI setup for iOS, not considering Android OS's.
Will keep you updated once I have some more information about previous versions of MMI.
Blame the cars not the phone.
My phone works 100% well and perfect with my Acura.
I've also had fun trying to get my E46 3 Series BMW ULF BT module to talk to the Atrix - has no issues speaking to an older Nokia phone. Anyway after a LOT of experimentation I've finally pinned down the root cause of the problem, text messages (SMS).
I've yet to figure out the specific trigger but it is either the number of messages or something in a specific message it doesn't like. I figured this out because I noticed the envelope icon coming up on the BMW screen for 5-10 seconds before the bluetooth would drop out each time after connecting the pairing. Each connection only lasts 15 seconds at most.
Anyway there were 193 SMS messages in the car memory, maybe the 194th message was upsetting it. I deleted almost all the 1150 SMS messages in my phone and it was only when I got rid of all of them that it connected. I then had to manually clear the SMS messages in the BMW one by one (took a long while).
I then did some testing whereby I sent an SMS or two to my phone. I noted that the Atrix seems to periodly get asked to upload messages to the car. You can delete them in the car but if they are still on the phone, they come back shortly after. They always show as unread on the BMW unless you read them on the car screen. Reading them on the phone has no affect. Maybe the SMS side of BT headset support is borked on the Atrix.
So my conclusion is that while I don't know the detailed trigger specifics, for BMWs at least the Atrix Bluetooth issue comes down to SMS messages. My large contacts directory uploads in its entirety without an issue. The solution for reliable BT connectivity to the Atrix and a BMW seems to be in SMS message management. Get yourself a copy of SMS Backup from the market when you experiment.
Hope this helps others!
Matt
A few days ago I bought a device called GMATE ($80), a type of smallcell without display or keyboard which is inserted a normal simcard and communicating via Bluetooth to the Samsung Galaxy Player, which means an application is integrated with android, receiving and making phone calls, and SMS, in addition to allowing internet access GPRS.
It's a perfect combination that increases the possibilities of Our Player
IPhones must be jailbroken, a repo is added to Cydia, and then the Gmate app is installed for the integrated Gmate functionality. How does this work in Android?
In GooglePlay you can download a Gmate aplication that integrates the gadget with your android player (also convert your android phone in a double sim phone) and uses android phone's features like dialer, contacts, or any thirtd party aplication likes rocket Dial.
Received and Make calls don´t need special features, if you uses the Gprs/edge to internet (in places with no WIFI) need to be rooted.
The application is not compatible with my U.S. 5.0 Player.
CreekDirt said:
The application is not compatible with my U.S. 5.0 Player.
Click to expand...
Click to collapse
Go to skyroam webpage and ask for a .apk file, i have Intl 5.0 and working great, sometimes any aplication in GooglePlay seems to be incompatible for my SG player but, on a external apk source works fine.
Dutch 5.0
Thank you for the info! I will definitely buy one if it works in The Netherlands.
That does look interesting.
Anyone using it with the USA version?
Is there something similar that i can connect it to my player or to put it in the galaxy player? So this wey i dony have to worry if i get out of 10 neters or jf i fodget it at home
Sent from my YP-G70 using xda premium
Wow, wonderful find. I was looking for exacly something like this. Unfortunately, With ICS CM9 installed on my GP5 Bluetooth doesn't work =( (neither does the camera or hardware acceleration. They really need to fix that.)
So I can make phone calls/sms without having wifi?
oncaribe said:
A few days ago I bought a device called GMATE ($80), a type of smallcell without display or keyboard which is inserted a normal simcard and communicating via Bluetooth to the Samsung Galaxy Player, which means an application is integrated with android, receiving and making phone calls, and SMS, in addition to allowing internet access GPRS.
It's a perfect combination that increases the possibilities of Our Player
Click to expand...
Click to collapse
With the Gmate app, can your SGP connect to a regular cell phone with bluetooth or it can only connect to the Gmate?
testrider said:
With the Gmate app, can your SGP connect to a regular cell phone with bluetooth or it can only connect to the Gmate?
Click to expand...
Click to collapse
Gmate only.. I tried it with my other android phone and it doesn't work.
I came further when I changed my phone's Bluetooth id to "Gmate". It didn't connect because of a password failure
It's seems good
I don't quite understand... So besides buying the Gmate, would i need a sim card as well? secondly so would i practically be using a sim card with a data plan to use with gmate? but wouldnt that defeat the purpose of just using a smart phone with a card in it?.... these are all continuation Q's if the first is a yes lol.
This seems like a stupid question, but I'll ask anyway. How well does the device actually work? Does it keep a connection throughout the day, sending and receiving text messages without too much delay? I'm considering using this to replace my old dumbphone, but I'd rather not plunk down a sizable chunk of change with little indication as to how well this thing actually works.
Gmate calling speaker sound
Question: Does the sound come out of the front speaker while calling?
(I don't like to call everywhere with loud back speakers)
crowelfly said:
Question: Does the sound come out of the front speaker while calling?
(I don't like to call everywhere with loud back speakers)
Click to expand...
Click to collapse
I don't know about GMate, but on Groove IP (and probably others), the front speaker on the 5.0 is quite functional and is used for calls.
Mevordel said:
I don't know about GMate, but on Groove IP (and probably others), the front speaker on the 5.0 is quite functional and is used for calls.
Click to expand...
Click to collapse
Thank you for the info!
P.S. I like your rom a lot!
Cool!
Sent from my YP-G70 using xda app-developers app
EDIT: I HAVE FIXED THE MAIN ISSUE WITH MY GMATE, MORE INFORMATION BELOW
Well, my Gmate+ came in the mail today, and I've been playing with it for a little while now and am able to give first impressions. First off, the device is much smaller than I imagined, it easily fits in my palm, the vibration (on the plus version) is very loud. As for the function itself, it works. You can call and send and receive text messages (haven't tested the web access yet) with a few minor (and one major) annoyances. My device is currently a US SGP 4.0 running Terrasilent 1.1 and EtherealRom 2.3.
Minor annoyances I have found with the Gmate+:
- Notifications (read: texts) do not make noise/vibrate while the screen is locked. Once the screen goes on, if you do have a new text, it notifies you, kind of ruining the point of the notification.
- Text messages you send have proper time stamps, for some reason, the ones you receive are off by a few hours, as if the sender is in a different time zone
- Seems to be no way to delete contacts from the address book, even uninstalling, wiping data, reinstalling didn't do anything about this.
Major annoyance with the Gmate+:
- It disconnects, and by that I mean it disconnects ALL THE TIME, the device is pretty much useless because of this, it will be fine for a few minutes, then disconnect, regardless of how close the Gmate is to my SGP. Every few minutes, I'd check it, and guess what? No connection. Sometimes it would reconnect, sometimes I'd have to manually do it, sometimes I'd have to restart one or both devices to get it to work again.
Seeing as everything the device does it actually does quite well when actually connected, I want to rule this problem to some battery saving tweak in my kernel/rom. As such, I'll be returning to stock and trying the Gmate again to see if any of these issues are cleared up. As it stands, I have a 75$ paperweight that buzzes occasionally.
EDIT: After flashing back to stock and noticing no change, I began searching around and found other people having similar problems with similar devices, mainly connecting their smartphones to the bluetooth sound system in their car. Turns out in Deep Sleep, the device has issues keeping constant bluetooth connection. After downloading an app (Bluetooth KeepAlive: ~$1.30) on the market that keeps the device from entering this mode, the Gmate no longer disconnects, and has remained connected for several days, having no problem with calls or text messages at any time. In summary, with this app, I am now happy to recommend the Gmate to anyone who is looking for this kind of functionality. Guess it goes to show that non compatible apps are listed in the Play Store as non working for a reason
Hello there,
I just got my Xperia Sola and wanted to use it for Voip calls using mobile voip. But the microphone volume is just too low for the opposite to properly understand me.
So I tried a bunch of other Voip apps, including the build-in one, Skype, and CsipSimple.
Always with the same issue, except that I can amplify the mic in CsipSimple, but this way the audibility is not much better since there is lot of noise.
Normal GSM calls work excellently, I also use the same internet connection and Voip Provider with my SIP landline phone or Notebook, and it always works perfectly. Mobile Voip also tells me I have excellent Network quality.
Is there any way to fix that or is it just something a Xperia Sola owner has to live with?
I have heard its a general android issue for pre 3.0 android phones. So there is hope it might work with the upcoming ICS update? If not what other similar phone would you recommend that definetly works? I was also thinking about getting an Xperia U or S instead since I still have time to return my sola but wonder if its not a general Sony xperia Issue.
Thanks for any reply in advance!
update:
So I was trying it again and now see that the error is a simple one, still dont know how to fix it though.
If I use any VOIP app, not regular handset mic is used but the one on the back of the phone, that is i guess meant for videorecording. So if i turn the phone around and talk in there, the person on the other side can hear me just fine...
anyone else maybe ever tried any voip app with the sola and knows if this is a general issue or just a bug in my sola?
Also... maybe anyone an idea how to fix that, some hidden setting in Android system maybe?
This thread should have been started in the Q & A section, kindly post in the relevant section next time. Thread closed.