Hi @ all,
since a few days i am a proudly HTC Hero owner. Its quite an amazing phone with many features and a steady growing Market.
At the weekend i tried to couple my Hero with my bluetooth handsfree set installed in my car. But what i recognized wasn't so much pleasing: The Hero didn't display the handsfree set in the list of available bluetooth devices.
Before i got the Hero i had a HTC TyTN II aka Kaiser and it worked well with the handsfree set.
Perhaps anybody else have some similar trouble or experience with this and maybe a solution, fortunately. It would be great to keep usage of my handsfree set furthermore.
Thank you and best regards
On handsfree there are some buttons right ? You need to press them in a combination so the handsfree can be detected by your Hero. Just search on the handsfree guide or internet. I cannot help you because I don't have it and don't know the button combination. When you find it go to settings and turn on Bluetooth on your phone. Just search it and connect to it
Hi omokas,
yes, you are right.. but i've done this.
The users guide says you have to press the main button for 1 second. After that you will get a feedback sound and the led gets flashing... so far so good.. everything is fine but the Hero doesn't recognize.
Hopefully there are no different bluetooth protocols or whatever the devices can't communicate.
Have you tried an application from Market ? It may to the job
But if not then your handsfree must be an older version that your Hero can't recognise. Before buying a new one make sure your phone works with other handsfrees.
Have you tried an application from Market ? It may to the job
Click to expand...
Click to collapse
No, i haven't tried yet. Can you recommend one?
At the moment i'm not able to try an other handsfree. But i've just seen the handsfree is able to store seven pairings... maybe there is the problem.
So i'm going to delete all pairings and give a next try.
Thanks
Yes try that. You could try the application "Bluetooth+Headphones".
Sorry if I am not able to help further but I don't use handsfree because I am 13 and I don't know how to drive.
No Problem... I am appreciate for any Help!
Did you get any results yet? E.g. did the removal of the other pairings work? Or the app from the market?
I'm quite interested in this since I'm still looking into getting the CK-100 build in my car
I am planning on getting that carkit wired up outside of the car, so I can at least give it a try and see if it wants to work. But don't have that much time to give it a try yet, end of next week perhaps...
I have a CK-7W and it works with my Hero (official orange ROM).
It was a bit of a nightmare to get paired in the 1st place, the hero failed to find it but I kept trying and it eventually found it. I think I might have reset the hands free though (pull the power for a few minutes).
The device usually pairs pretty fast, sometimes it takes a min or two but not often.
My only gripes are :
1: some times it doesn't send the audio to the speaker keeping it on phone requiring you to use a menu option to do so.
2: The ring tone isn't the one set on the phone but a generic ringer.
3: Occasionally the phone doesn't disconnect properly when the other end hangs up requiring you to do so manually.
I have a CK-15W car kit
and its fully supported
it even downloads the phonebook very well
ck7w and hero
My hero worked first time! To pair you need to leave ignition off and hold the button in until it beeps, not just a short push as that just turns the car kit on. Once its beeped search for it and then pair using code. As yet I have had none of the problems mentioned here. I hope this helps
I have the same phone (Android 1.5 stock ROM) and the same Nokia CK-7W handsfree set.
For me this works fine. Didn't have to press the button on the handsfree set. Just searched for BT devices and paired.
Hello,
We are trying unsuccessfully to get Rsap working and was wondering if maybe anyone here can help..
What I’ve done:
I have rooted the HTC EVO 3d successfully and Android super user is working correctly.
I have successfully installed the installation files, following these instructions: android-rsap / installation
I have purchased the app and installed it.
When I start the app I see the following:
Bluetooth state:
not connected
STP records not fixed
SIM state:
Normal phone operation
Then we tried to connect it to the Audi MMI, I have followed other forum instructions and deleted all old pairing links on the phone and MMI.
I make sure the Bluetooth on the phone is discoverable and search for the phone via the MMI.
The phone is found but when we try to make a connection I only have the options: hands free or Music player…. No sap profile.
I tried to first make a hands free link and then try to find a sap profile on the MMI to no avail..
I have tried all possible scenarios with pairing the phones but I do not see a SAP profile.
When connected to the MMI in hands free mode all the Rsap settings on the phone seen above stay the same, not connect or fixed.
Am I missing something? I have read that a sap paired connecting need a x16 long password handshake?
Do I need to activate something on the MMI or phone to bring up the sap profile on the MMI?
Ps: the MMI is from the new Audi A8 and is Rasp compatible, I do see an option on the search for new telephone screen on the MMI: connect a telephone or add SIM. Unfortunately I cannot select this.
Grateful for ANY help!!!
Thanks,
John
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Update:
I have the same thread running at the Rsap developers site, I got an answer from who I think is the developer:
“It looks like the Audi A8 is also a victim of the "SDP fix" problem, like the Porsche PCM. Sadly I did never have a chance to test the app with an A8 myself and I don't get much feedback from Audi drivers. Although it seems to run with an A6 with HTC stock ROM. You may try to flash an AOSP custom ROM like CyanogenMod, this does not have the "SDP fix" issue.
The next problem is probably bigger: No one confirmed so far that the HTC EVO3D works at all with my rSAP app. Since the phone is quite similar to the HTC Sensation chances are high that it will not.”
So that’s unfortunate, but I was wondering if anyone knows of a ROM etc. that does allow RSAP?
Thanks again for any help,
John
Nobody with the EVO 3D GSM has any rSAP knowledge?
I was hoping to find someone on such an active forum..
Anybody know of a ROM for the GSM version without the SDP fix problem?
Thanks,
Hello,
I have ICS beta 2 lite installed (Android Version 4.0.1 Baseband S5830DDKQ5 Kernel 2.6.35.7-perf-CL514579 ketut )
But although the phone says its paired with bluetooth devices it wont connect
Is there a fix or do I need to go back the Ginger Bread?
Thanks in advance.
(I have tried 'search' but I'm not finding any answers)
Superheavy1203 said:
Hello,
I have ICS beta 2 lite installed (Android Version 4.0.1 Baseband S5830DDKQ5 Kernel 2.6.35.7-perf-CL514579 ketut )
But although the phone says its paired with bluetooth devices it wont connect
Is there a fix or do I need to go back the Ginger Bread?
Thanks in advance.
(I have tried 'search' but I'm not finding any answers)
Click to expand...
Click to collapse
First of all, it's NOT ICS ...it's gingerbread
It's based on 2.3.5 (developer has just changed it to 4.0.1)
Second,
Bluetooth works fine for me
Ayushbhatiapro said:
First of all, it's NOT ICS ...it's gingerbread
It's based on 2.3.5 (developer has just changed it to 4.0.1)
Second,
Bluetooth works fine for me
Click to expand...
Click to collapse
Please accept my apologies. I was relaying the info from the handset.
I'd be grateful if you would tell me what settings/options you have 'on' and 'off' so that bluetooth pairs, connects and works with bluetooth devices such as headset, sat nav etc
Thanks again.
Bluetooth ICS reconnecting Audio
I'm having a similar problem.
When I connect to my car stereo via bluetooth the first time (since a reboot) and it will play. However whenever my phone reconnects after that, it will pair and I can use the A2DP interface on my car deck to play/pause/etc but the audio will play on my phone speaker and not transfer to the car stereos like usually. Once rebooted, everything will work the first time again.
I've never had this problem before. I am looking into it right now and will let you know when I figure something out .
guys wait for final version...
the developer of Myth ics has removed the previous rom since it had bugs..
so there is no point in complaing
he is trying his best for making new rom free of bugs
wait for it
I'm not complaing. I'm asking for help. I asked you what settings you have chosen regarding bluetooth which so far you have ignored for whatever reasons.
Instead of being helpful your replies have been obtuse and obnoxious. Loose the attitude geek-boy.
People are asking for help NOT criticising.
.
Superheavy1203 said:
I'm not complaing. I'm asking for help. I asked you what settings you have chosen regarding bluetooth which so far you have ignored for whatever reasons.
Instead of being helpful your replies have been obtuse and obnoxious. Loose the attitude geek-boy.
People are asking for help NOT criticising.
.
Click to expand...
Click to collapse
I am sorry dude .i was not rude .....I have changed this rom long back ..so I don't know settings ....hope someone helps you ..sorry I have used the word complaing I didn't mean it
You know the case of jasuda ? Noobs asking foolish questions
I a NOT saying you are an noob (but am angry at noobs ),you had a problem so you asked it ,it's ok it's not only you who is facing problems there are many
I use Bluetooth rarely ,I used for 2-3 times and it worked
Sorry again ,
Apology accepted. Thank you.
Superheavy1203 said:
Apology accepted. Thank you.
Click to expand...
Click to collapse
awwww you guys lol.....what devices are you trying to pair with heavy? I need some more info so I can help
plantronics headest (supplied by vodafone)
Tomtom sat nav
any bluetooth device I try but those two are what I use most.
I have figured out a work-around for the auto pairing failure. I will give a step by step workaround how I did it. In my situation, I have a Mazda CX-5 and a Samsung Galaxy S3. But I am confident, that it will work with all Android 4.0.4 versions and other carkits, because the problem is most likely the same issue.
The reason why the phone won't auto pair, is because the phone does not give your carkit permission to download call history and other data. Even if you granted the phone this permission with the initial pairing.
If you have a carkit that supports multiple bluetooth profiles (multiple phones), like my Mazda CX-5 does, then you can also have your phonebook downloaded to your car. If your carkit supports multiple profiles, start with step 1. If yours doesn't, start with step 7. This guide is specifically for the Mazda CX-5, so some steps may be (slightly) different for your car model or make.
Here is the step by step guide:
1. Make sure you have no existing bluetooth pairs. Clear all pairs in your carkit and your phone.
2. Pair the phone with your carkit. You can see the randomly generated code on your phone and on the car display. Press ok to pair. (other carkits may need you to input "0000" or "1234", or maybe you have to input a code yourself)
3. Your phone will ask 2 questions about permissions. Check the box and allow. The phone will start to sync.
4. You carkit is done with syncing and it will ask you if you want to download your phonebook. Do this.
5. When its done copying, clear the Bluetooth pair on your phone (not on the Carkit!)
6. Give your phone a different Bluetooth name
7. In your carkit choose to pair a new phone (with the new name you just entered).
8. When the phone asks for permission for the carkit, check the box and choose cancel. Do this for both questions.
You don't have to copy your phonebook again (you can't anyway because you denied permission), but the phonebook that was downloaded earlier will still be available. Now the phone will pair automatically! With this trick you have your phonebook and automatic pairing.
I haven't seen what this does for media-audio streaming. I don't use that, but I can image that it doesn't work, because of the denied permissions.
There is another downside to this though (there always is, isn't it?). You cannot update your phonebook easily. If you want to update your phonebook, repeat the whole procedure.
I hope this will work for other people with different phones and cars too. At least this is a workaround until Google/Samsung comes with a fix. Please let us know if this works in your situation. To keep things structured, please use this format:
Car: Mazda CX-5
Phone: Samsung Galaxy S3
Works: Yes
That's OK !!
Car : Renault Scénic
Phone : Samsung Galaxy S3
Works : Yes, fine !! (with the MP3 reader too !...)
Good stuff!
Car: Vauxhall Vivaro van
Phone: Samsung Galaxy S3
Works: Yes, but can't get access to the phonebook as bluetooth keeps dropping out before it downloads. I don't really mind that though. At least I can now use my phone!
Man thanks for this fix!
DJ41 said:
I have figured out a work-around for the auto pairing failure. I will give a step by step workaround how I did it. In my situation, I have a Mazda CX-5 and a Samsung Galaxy S3. But I am confident, that it will work with all Android 4.0.4 versions and other carkits, because the problem is most likely the same issue.
The reason why the phone won't auto pair, is because the phone does not give your carkit permission to download call history and other data. Even if you granted the phone this permission with the initial pairing.
If you have a carkit that supports multiple bluetooth profiles (multiple phones), like my Mazda CX-5 does, then you can also have your phonebook downloaded to your car. If your carkit supports multiple profiles, start with step 1. If yours doesn't, start with step 7. This guide is specifically for the Mazda CX-5, so some steps may be (slightly) different for your car model or make.
Here is the step by step guide:
1. Make sure you have no existing bluetooth pairs. Clear all pairs in your carkit and your phone.
2. Pair the phone with your carkit. You can see the randomly generated code on your phone and on the car display. Press ok to pair. (other carkits may need you to input "0000" or "1234", or maybe you have to input a code yourself)
3. Your phone will ask 2 questions about permissions. Check the box and allow. The phone will start to sync.
4. You carkit is done with syncing and it will ask you if you want to download your phonebook. Do this.
5. When its done copying, clear the Bluetooth pair on your phone (not on the Carkit!)
6. Give your phone a different Bluetooth name
7. In your carkit choose to pair a new phone (with the new name you just entered).
8. When the phone asks for permission for the carkit, check the box and choose cancel. Do this for both questions.
You don't have to copy your phonebook again (you can't anyway because you denied permission), but the phonebook that was downloaded earlier will still be available. Now the phone will pair automatically! With this trick you have your phonebook and automatic pairing.
I haven't seen what this does for media-audio streaming. I don't use that, but I can image that it doesn't work, because of the denied permissions.
There is another downside to this though (there always is, isn't it?). You cannot update your phonebook easily. If you want to update your phonebook, repeat the whole procedure.
I hope this will work for other people with different phones and cars too. At least this is a workaround until Google/Samsung comes with a fix. Please let us know if this works in your situation. To keep things structured, please use this format:
Car: Mazda CX-5
Phone: Samsung Galaxy S3
Works: Yes
Click to expand...
Click to collapse
This does not work for my 2010 Altima, but glad to hear someone is able to fix their problem. Maybe I should go buy a Mazda :good:
POSSIBLE SOLOUTION
Guys, this problem was driving me nuts, just like many it worked the FIRST time it synced with my car but after that no go ! i randomly was trying stuff until something odd happened, i installed this program : https://play.google.com/store/apps/details?id=it.medieval.blueftp&hl=en and tried connecting to my car within the program, from now on, as long as that program is running, EVERYTHING is working, i can even get to my Text Messages from my car , all good !!! hope this helps you guys.
Running AOKP ROM on Rogers S III.
Cheers,
DJ41 said:
I have figured out a work-around for the auto pairing failure. I will give a step by step workaround how I did it. In my situation, I have a Mazda CX-5 and a Samsung Galaxy S3. But I am confident, that it will work with all Android 4.0.4 versions and other carkits, because the problem is most likely the same issue.
The reason why the phone won't auto pair, is because the phone does not give your carkit permission to download call history and other data. Even if you granted the phone this permission with the initial pairing.
If you have a carkit that supports multiple bluetooth profiles (multiple phones), like my Mazda CX-5 does, then you can also have your phonebook downloaded to your car. If your carkit supports multiple profiles, start with step 1. If yours doesn't, start with step 7. This guide is specifically for the Mazda CX-5, so some steps may be (slightly) different for your car model or make.
Here is the step by step guide:
1. Make sure you have no existing bluetooth pairs. Clear all pairs in your carkit and your phone.
2. Pair the phone with your carkit. You can see the randomly generated code on your phone and on the car display. Press ok to pair. (other carkits may need you to input "0000" or "1234", or maybe you have to input a code yourself)
3. Your phone will ask 2 questions about permissions. Check the box and allow. The phone will start to sync.
4. You carkit is done with syncing and it will ask you if you want to download your phonebook. Do this.
5. When its done copying, clear the Bluetooth pair on your phone (not on the Carkit!)
6. Give your phone a different Bluetooth name
7. In your carkit choose to pair a new phone (with the new name you just entered).
8. When the phone asks for permission for the carkit, check the box and choose cancel. Do this for both questions.
You don't have to copy your phonebook again (you can't anyway because you denied permission), but the phonebook that was downloaded earlier will still be available. Now the phone will pair automatically! With this trick you have your phonebook and automatic pairing.
I haven't seen what this does for media-audio streaming. I don't use that, but I can image that it doesn't work, because of the denied permissions.
There is another downside to this though (there always is, isn't it?). You cannot update your phonebook easily. If you want to update your phonebook, repeat the whole procedure.
I hope this will work for other people with different phones and cars too. At least this is a workaround until Google/Samsung comes with a fix. Please let us know if this works in your situation. To keep things structured, please use this format:
Car: Mazda CX-5
Phone: Samsung Galaxy S3
Works: Yes
Click to expand...
Click to collapse
Car: Honda Accord 2011
Phone: Samsung Galaxy S3
Works: NO
I have many problems with paring the S3 to different devices (headset, carkit, modem) Even connecting the S3 to my Galaxy Tab 7.7 reuslts in the S3 not being able to sent photo's to the Galaxy Tab 7.7 only when I fist sent a foto from the tablet to the S3 I can then sent form S3 to tablet. Also Wifidirect does not work. The software of my S3 is:
Android: 4.0.4
Baseband: i9300xxlfb
Kernel: 3.0.15-782020-user
Buildnummer: I9300XXBLFB
Any discussion with Samsung support and product managers did not resolve in a solution, they continously point the issue to the carkit, headset, modem supplier. Even the problem with connecting to the Samsung tablet is waved as "Differnt software, different hardware no guarantee that is compatible".
Solution
So I have reset the S3 back to factory settings which removes all apps not installed by me and all personal settings. Then I did following:
I installed, on the Samsung Galaxy S3 the first version of Samsung factory ROM (Build I9300XXALE8 for region Europe which is also 4.0.4 but the earlier version) using procedures and software(odin) to install custom roms. This does not void the warranty as the unit is not being rooted but only downgraded to an earlier official Samsung softeware
Then reset the S3 again to factory default settings.
Started the pairing with the Bluetooth device. They all started to pair and work correctly.
Removed all pairing profiles again form the phone and tried to pair again.. it kept doing the right thing.
Turned off the phone, turned on again and autopair with the carkit worked flawless. (my carkit is a Pioneer HD1BT). Same with headset and modem.
Install Samsung automatic software updates which upgrades the device ROM to newest version Build I9300XXBLFB. Manual disconnect and reconnect kept working
If one removes any BT connection profile on the phone after the software update, the BT connection/pairing problems with that device will come back and you need to do the whole procedure again
Bottomline conclusion: The latest Samsung updates has broken the ability to create a pairing profile with some bluetooth 2.0 devices.However, once the phone has Bluetooth connection profile for that the device, it keeps working.
The blame of Samsung towards carkit mfg's is incorrect. . It also has nothing to do with Bluetooth 4.0 compatibillity with 2.0 devices. (iPhone 4S, HTC One X are bluetooth 4.0 and the HTC One x is also Android 4.0.4). It is a pure Samsung sofware problem!
Either way It sucks. This is supposed to be the best phone on the market and its not without bugs
I received an OTA from Sprint and my bluetooth is now working as intended in my car. Have others received this OTA and had their bluetooth issues resolved?
I'm having a similar issue, but it only fails to autoconnect once I have set it to use the phone as a Bluetooth audio device.
Car : Volkswagen Golf (Rabbit) GTD
Phone : Samsung Galaxy S3
Works : Yes but can't sync contacts
All worked fine with LFB ROM (auto pairing and contacts sync) but from LG6 (LG8, LG9 and LH1) my phone disconnected 5sec after a contacts sync and auto reconnect 1min later...
So I just paired the phone without contacts synchronising.
Good news for everyone : everything works fine with JB (contacts, auto pairing...) !
Soon on Criskelo ROM :good:
Bluetooth woes
Erwan960 said:
Good news for everyone : everything works fine with JB (contacts, auto pairing...) !
Soon on Criskelo ROM :good:
Click to expand...
Click to collapse
Which JB Rom did you use?
mikeinstlouis said:
Which JB Rom did you use?
Click to expand...
Click to collapse
LH7 today but still problems in fact. I had a very lucky test... cause today it's impossible to synchronize contacts correctly without being disconnected every 10 secs.
All I can do is pairing S3 and car kit without contacts...
I think I found a solution that seems to work well for me. I tried 3 times and it works.
I tested one last time just leaving a blank LH7 stock ROM then a nandroid backup from a previous version and if it is confirmed, I will explain the process. :laugh:
I solved the problem! (at least with my config)
For those interested it's in french here : http://www.tmaddict.com/forum/viewtopic.php?f=218&t=25446&p=332863#p332863
If you need help to translate, just ask !
Robmtx said:
I received an OTA from Sprint and my bluetooth is now working as intended in my car. Have others received this OTA and had their bluetooth issues resolved?
Click to expand...
Click to collapse
I just installed the Tmobile OTA update and verify that the bluetooth reconnection issue has been resolved. I was using the workaround prior to this update and it worked as stated. After the update, I removed the pairing profile and re-pair from scratch and it worked right away. My issue now is that only a small portion of my (google) contact list gets transferred to the car. If anyone has any suggestions on workaround, it will be much appreciated
Stupid question but we never know... : did you wait long time enough ?
Check your google contacts and avoid :
- *
- non-ASCII characters
- email addresses with 'home' or 'work' attribute
With a little luck ...
Ive been trying to figure this out now for a month and so far i have found:
If i restore back to stock image (rooted) with samsung bloatware bluetooth will work perfectly fine.
If i then go to use TB to restore all my apps data etc, whenever i get into the car i will then get aprox 30 seconds - 2 minutes delay in the pairing.
If i restore back to stock and just use phone book it works perfectly fine. So i wondered if something was in the restore.
If i then flash a custom rom (any rom 4.0.4) on it will just take 30 mintues or whatever the timeout i have set in the bluetooth config file, this in theory is a dead end does nto work. If i then reflash the custom rom and do a complete user wipe, fix perm and nuke all the cache it then works perfectly fine with the custom rom (exactly like the stock).
I then can go to the car and it will pair perfectly. If i then go to TB and restore (including bt pairing etc) i get stuck in the 30 -2 minutes pairing, sometimes even longer.
Now here is the strange part, if i know my phone is at the stage where it will pair within 2 minutes i know i can restart my phone and it will pair instantly! If i turn off BT and turn it back on it will not pair.
OK so now i kind of know how to get it working but not as perfect as walking to the car and it pairs within a second or two. If i then flash a kernel (any i have tried about 4 of the popular ones) i then get 0 pairing, it can try for 10 minutes - 20 minutes it will just not pair. I then have to reflash over on top the custom rom with full bloatware.
Ok so now if i try the same as above minus the bloatware i get stuck in the non pairing mode again. non of this install bluetooth.apk, pressing cancel to contacts works for me. My BMW, AUDI will just get stuck in limbo where its paired but the connection is similar to a phone call for an unlimited lengeth of time it will just not work.
My current state of the phone is like this... OMEGA ROM (any version 4.0.4), stock kernel, FULL bloatware and my phone will pair either instantly or <2minutes. If it fails to do this a restart of the phone will pair it instantly.
I am able to freeze bloatware but any removal and the BT just hits deadlock. Now what is weird is i never ran my phone with bloatware at all up until all these problems started so something in the last month has sent my bt messy. even restoring back to my rom backup from when it was workign wil lnot fix it.
This is not a car BT issue as i have tried three cars and they work perfectly fine with any other phone.
I am getting kind of sick of sitting in the car flashing roms, trying things etc. I do not know what the problem is but atleast 2mins waiting time is better than not having anything
I'm on JB (Revolution HD 12.2) and my S3 still won't pair with a car kit, no matter what I do. :\
I just received this tablet with 3g stick - i would use it also for voice call not in internet but through the sim because i had a full phone plan with voice and internet -
i know that other tablet like sam.... with a software patch had enabled voice function -
we have to wait for a software upgrade or there is an hardware problem ?
in this case there is another usb modem with this function ?
thanks for your attention
newmave said:
I just received this tablet with 3g stick - i would use it also for voice call not in internet but through the sim because i had a full phone plan with voice and internet -
i know that other tablet like sam.... with a software patch had enabled voice function -
we have to wait for a software upgrade or there is an hardware problem ?
in this case there is another usb modem with this function ?
thanks for your attention
Click to expand...
Click to collapse
Hi There,
As far as I know the Archos 3G Stick is lacking voice capability at an hardware level so that is a no go, It theoretically possible using a Patched Huawei Dongle, I got it to successfully connect a silent call when I was playing around with it, It could be just a case of wiring up the audio policies in Android or something vastly more complex, I didn't bother investigating further. You also need to patch your framework-res.apk to make the rom voice_capable, you can also make it sms_capable as well, this allows you to use the stock mms app for sending and receiving messages
You might want to do a search before posting, because this question has been asked before and there's a couple of development threads regarding it, One is linked from my signature.
Thanks
trevd said:
Hi There,
As far as I know the Archos 3G Stick is lacking voice capability at an hardware level so that is a no go, It theoretically possible using a Patched Huawei Dongle, I got it to successfully connect a silent call when I was playing around with it, It could be just a case of wiring up the audio policies in Android or something vastly more complex, I didn't bother investigating further. You also need to patch your framework-res.apk to make the rom voice_capable, you can also make it sms_capable as well, this allows you to use the stock mms app for sending and receiving messages
You might want to do a search before posting, because this question has been asked before and there's a couple of development threads regarding it, One is linked from my signature.
Thanks
Click to expand...
Click to collapse
Correct. Sim cards do not have the phone radio in them. Its the device itself. Therefore, other than using voip phone apps there is no way to make voice call on the tablets, besides my galaxy note.
Sent from my ARCHOS 80G9 using xda app-developers app