Do any of these ROMs allow skype or heytell use, I realize there is no internal mic, but external mics see some limited use with the stock rom.
Thanks for the info.
tablelegs said:
Do any of these ROMs allow skype or heytell use, I realize there is no internal mic, but external mics see some limited use with the stock rom.
Thanks for the info.
Click to expand...
Click to collapse
Honestly I can't think of many reason why any of them wouldn't support it. The functionality is present on the device and in the roms (at least in the cm7 and cm9, I know nothing about miui but I can see little point in removing it). The real question is; 'does it work'? to that end you will probably to best testing. I don't have a headset mic to test with anymore for example or a skype account for that matter. Try the CM7 builds I have up if you like, they are here. If you find it doesn't work drop me a post on that thread I'll research it.
Thanks for the update. I was running CM7 then switched back to the remixed stock ROM. I will reinstall cm7 now and report back.
Heytell works perfectly, skype ends the call as soon as it is placed making me think that skype itself does not like the kindle fire.
A new version of Skype is required to run on an Android device with external mic such as KF
Sent from my Amazon Kindle Fire using Tapatalk
Related
Anyone else running this and having issues with BT?
Blue tooth enables fine, but will not detect any of my BT devices.
i know its just a beta, but it says BT is working.
i would post this in the CM7 forum, but not enough posts in general to be able too.
I had an issue with it accepting the pin codes. You have to type it fast!!! took me at least 10 attempts to get it to pair but it works just fine once the codes in.
mpgrimes said:
Anyone else running this and having issues with BT?
Blue tooth enables fine, but will not detect any of my BT devices.
i know its just a beta, but it says BT is working.
i would post this in the CM7 forum, but not enough posts in general to be able too.
Click to expand...
Click to collapse
Hi I dont you use bluetooth but you can forward this in the development section on this forum there is a cm7 beta 3 thread
http://forum.xda-developers.com/showthread.php?t=929666
or better still try Elelinux's rom base on cm 7 which I am currently using ... Just love it
http://forum.xda-developers.com/showthread.php?t=932377
its working fine now, for some reason the phone wouldnt detect any BT device (want trying to detect the phone with other devices) , but i thought what the hell, i enabled the discoverable option, and it started picking up other devices, even now that discoverable is turned off its working fine.
dont know if it was that, but thats the only thing different i did, and now it works.
tfn said:
Hi I dont you use bluetooth but you can forward this in the development section on this forum there is a cm7 beta 3 thread
http://forum.xda-developers.com/showthread.php?t=929666
or better still try Elelinux's rom base on cm 7 which I am currently using ... Just love it
http://forum.xda-developers.com/showthread.php?t=932377
Click to expand...
Click to collapse
I don't know which one is better, any suggestions between 2 ROM there?
I bought the Mini Bluetooth Keyboard direct from Chinavision. It works OK in WInMo, but nothing will make it work in Android. I would post the link, but posting rules don't allow it.
Has anyone else bought a similar keyboard (I believe they sell a similar one on Amazon) and got it to work? If so, how?
I can pair it OK, but nothing will make it work. I tried the supplied Android driver, but that won't install properly. I tried the various BlueInput apps, but none will connect at all.
Chinavision themselves are not at all co-operative, so I thought I'd ask here.
Thanks in advance,
--
Pete
Just ordered something simular on ebay and waiting for delivery.
I noticed it said that it wouldn't work in Android v2.2 so I guess it will be a bit of a challenge to get it working.
I tried again today. I installed BlueInput v1.8 and had some results, but nothing useful. A click sound comes from the HD2 every time a key is pressed, as per the settings, but no text.
So, something is happening ...
I'm running darkstone SuperRAM Froyo 1.5 on SD.
--
Pete
use cm7. cm implemented support for bluetooth hids.
lolmensch said:
use cm7. cm implemented support for bluetooth hids.
Click to expand...
Click to collapse
cm7?
---
Pete
PeteMy said:
cm7?
---
Pete
Click to expand...
Click to collapse
cyanogen mod 7. it is a popular custom rom. (cyaongen mod 6 will also work but there are almost no roms around here anymore.)
Viber is out! Trouble is, ZTE Blade 2.2 is not supported, it seems.
With vanilla 2.2 i can't find it in market, but in the web-based market they say my phone isn't supported.
With CM7 i can find it in market, install it without problems, and make a call. However, i can't hear anybodys voice.
Does anybody know of a workaround or at least a possible reason?
Kame_boy said:
Viber is out! Trouble is, ZTE Blade 2.2 is not supported, it seems.
With vanilla 2.2 i can't find it in market, but in the web-based market they say my phone isn't supported.
With CM7 i can find it in market, install it without problems, and make a call. However, i can't hear anybodys voice.
Does anybody know of a workaround or at least a possible reason?
Click to expand...
Click to collapse
I got it Froyo SS5/Gen2.......on market and web OK.....
But, when installed, it has the old problem of the sound being routed to the Speaker, regardless whether Speaker selected or not.....
Also, made call to iPhone Viber User, sounded OK my end, through Speaker, but iPhone user says Echo/delay, Bad Quality....
You gotta FC to Exit App, no other way out!!!!
Going to stick with CSipSimple, works on my Blade, sound is routed perfectly, quality, not too bad.
irishpancake said:
I got it Froyo SS5/Gen2.......on market and web OK.....
But, when installed, it has the old problem of the sound being routed to the Speaker, regardless whether Speaker selected or not.....
Also, made call to iPhone Viber User, sounded OK my end, through Speaker, but iPhone user says Echo/delay, Bad Quality....
You gotta FC to Exit App, no other way out!!!!
Going to stick with CSipSimple, works on my Blade, sound is routed perfectly, quality, not too bad.
Click to expand...
Click to collapse
Do you think the sound quality only depends on the SIP/VOIP client, or the provider also matters?
I've never seen a dedicated thread on this but I've seen people make off-hand comments about this issue from time to time. I think it started happening in Tytung R9 and higher kernels.
I am using a BlueAnt T1 Bluetooth headset. It pairs just fine and I can use it generally without any issue.
The problem comes when I use voice dialing to initialize a call from the Bluetooth headset. It connects to the phone and I get the normal Android "Speak now...." I speak my command "Call <person> on <service>...." It states the command back like normal and then _as soon as_ it switches to the phone app (eg, com.android.phone process) it locks up the phone and the only way to recover is to pull the battery.
If, instead, I go to the phone app, find the person, and call them that way (even with Bluetooth paired) it _always_ works without any problems. This isn't a long-term solution for me because I need to use voice dialing when I'm in my car.
Now that GPS looks to be fixed and CLK data over PPP is much more stable, this Bluetooth issue is the last thing standing between me and treating the HD2 as my full-time native Android phone (currently I tinker on the HD2 but use my Nexus One as my daily driver).
I've tried multiple different ROMs, from HyperDroid-CM7, HyperDroid-GBX, Typhoon CM7, and Nexus-HD2-Gingerbread. They all have the same issue though Nexus-HD2 appears to be worse than the others (that is, the problem happens more often there).
I've used the infamous audio.conf update as well as the various no-wonk and libaudio patches and none of them help this issue.
Anyone else experienced this and have any feedback on how you overcame it?
I have the same kind of problem and tried a lot of different ROMs - not help.
I tried Blueant ST3, Motorola t305.
Phone book copied to blueant very well, but voice dial has same simptoms like yours - even if phone does't hang sound goes away from phone permanently(needs reboot). Is there any other ROM which works well with bluetooth hadsfree?
Any one?
P.S. Looks like it is real problem, but non of developers pay attention to it - they just don't have handsfree maybe
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
clio94 said:
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
Click to expand...
Click to collapse
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
svet-am said:
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
Click to expand...
Click to collapse
I think it is not the kernel, same kernel will crash in CM7 but no in CM6. I think the problem is related to the libaudio.so and other libs in system/lib.
robrob777 said:
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
Click to expand...
Click to collapse
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
svet-am said:
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
Click to expand...
Click to collapse
I'm using it as my daily driver (CM6), I came back just bc of the calling issues in Gingerbread.
the build that I'm using has not been updated since Jan 7, however I applied around 10+ patches and now it works as good as the new builds.
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
robrob777 said:
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
Click to expand...
Click to collapse
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
i just verified the problem exists in MIUI as well. I tested MIUI since it's allegedly a "clean room" type of build environment.
svet-am said:
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
Click to expand...
Click to collapse
Yes, I tested successfully in a Froyo based ROM.
I went back for a moment to CM7 and tested...sound couldn't return to the phone after calling with BT, also during the call I was not able to switch to speaker phone like I do in the froyo based ROM.
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
zcdg said:
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
Click to expand...
Click to collapse
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
svet-am said:
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
Click to expand...
Click to collapse
Yes you are right. It is just what Tytung said(i asked in his thread). Probably he meant GB for HD2....Soon or later they will figure it out i think...
For now will use Froyo 1.9G....
tytung said:
I don't have any Bluetooth headset.
AFAIK, some people have the sound issues, e.g. causing the phone app FC, since using Gingerbread 2.3.4.
But it doesn't affect all people, I don't know why.
No solution so far. To use Gingerbread 2.3.3 instead if you are one of them.
Click to expand...
Click to collapse
I finally found Tytung's exact quote as to why he won't look into the issue. It can be seen in context over here: http://forum.xda-developers.com/showthread.php?t=905060&page=524#
So, it might not be Froyo that's the fix but rather older versions of Gingerbread as well.
i have found a workaround fix for this bug.I tried it in tytung`s v2.9 rom and in dorimanx cm7 light rom with driztee v2 libaudio file.For bt voice commands i am using cyberon voice commander because google app doesnt support yet greek language
i connect my bt headset (motorola h300) and then i use super bt mono froyo free app https://market.android.com/details?id=com.steven.supermonofroyofree&feature=search_result to send audio to bt headset.
After pushing the bt headset button cyberon voice starts and i can give the command i want.After giving the command, audio goes back to the phone (you will hear a beep from phone speaker).The weird thing is that the audio is in extremely low level for hearing music but when you receive a call it is in normal level.
If i close super bt mono froyo app,audio returns to phone in normal level.
But if i accidentally (after i close the app) push the button for voice bt command,audio will disappear.
If the app is on and you receive a call,all audio will go again to bt headset and to return it to phone speaker after end call, i push bt headset,cyberon voice starts and i dont give any comand.After cyberon ends,audio goes back to phone with low level for media hearing.
Sure this isnt the perfect solution,but the important thing for me is that with this way,audio is not go away and i can give bt voice commands.
Also i tried bt mono app http://forum.xda-developers.com/showthread.php?t=950472 and it have a little different behaviour.I cant start from bt headset cyberon voice comander,but only from the phone and after giving a command,audio returns to bt headset if you have enable the setting "restart after call".So i think it maybe be helpful to people who want to have audio all time in a bt carkit.
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
zcdg said:
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
Click to expand...
Click to collapse
thanks for that follow-up and testing. I was wondering if whether or not it might be a "fault" in the VoiceDialer.apk or even in the Phone.apk. I have been using my Nexus One for daily stuff. I might try replacing VoiceDialer and/or Phone.apk in a newer ROM (eg AOSP 2.3.5 or so) with the old version and see if it works.
Ive wondered about this as it is to me the last issue I have with my HD2. Here is a search link for some entries in Tytungs rom & kernal thread...
http://forum.xda-developers.com/search.php?searchid=86308155
Also here is a comment from the man himself...
http://forum.xda-developers.com/showpost.php?p=15996942&postcount=5953
and here is a post in reply that talks about the same issue being replicated using Bluetooth...
http://forum.xda-developers.com/showpost.php?p=15997234&postcount=5956
Some more chat about the sound issues...
http://forum.xda-developers.com/showpost.php?p=16113973&postcount=6045
Another thread with logcats on it...
http://forum.xda-developers.com/showthread.php?t=1060486
Hey guys
I'm using my nexus 7 dashed in my car. (Kinda!)
And i'm using tablet talk to connect my phone with it.
Also i have a bluetooth keyboard connected to my tab.
When i have a text, i can answer it easily. But when someone calls me and i accept the call the sound doesn't come from my car audio and my sound doesnt go through my tablet's mic. They bouth go through my phone!
So i have to use my n7 as a bluetooth headset for my phone. Is it possible?
Can anyone guide me?
No one? nothing? no helps? no ideas? cool!!! :|
For God's sake!!!
guys, this will be great. pleeeaaaase, consider developing or sth.
Cool it, seriously. The forum hardly revolves around this one post.
Given the way the Bluetooth radios are set up, it's not really an easy hack and you'd probably have better luck using a dedicated app over Wi-Fi direct or something (of course, such an app would have to exist as well in the first place). I remember looking into this for the iPod Touch a while back and didn't see anything either, but hopefully you'll have better luck.
Rirere said:
Cool it, seriously. The forum hardly revolves around this one post.
Given the way the Bluetooth radios are set up, it's not really an easy hack and you'd probably have better luck using a dedicated app over Wi-Fi direct or something (of course, such an app would have to exist as well in the first place). I remember looking into this for the iPod Touch a while back and didn't see anything either, but hopefully you'll have better luck.
Click to expand...
Click to collapse
Well it WAS an easy hack, It's just a case of setting the configuration files up correctly. You get the N7 to advertize the Headset service and an Roberts your father brother as they say. I just about had it setup a couple of months back...... I want to control the full telephony service through the N7 show incoming calls and all the fun stuff.... As a first step I got the voice routing through the N7 Microphone through a handset and onto the caller. However I stopped there because that was using android 4.1.1 and I want to be using the latest build... Which is where your right out of luck because 4.2 onwards is a different beast,
Google decided to replace a tried and tested well documented fully implemented Bluetooth Stack with something that's not quite finished yet whose documentation is the source code. That's why there's no Low Energy stuff on Android yet..... It could and should have been implemented last year, anyway I digress. So the options are
1. Use a rom prior to 4.2 - In which case the Bluez is well documented and this sort of problem has been solved multiple times on the linux desktop and the same ideas can be applied to Android, Google is your Friend
2. put the old stack back in and work with that, There's patches that do that but they are all a bit brutal and would be a nightmare to maintain.,
3. Wait for the Missing Code to be added, which could be tomorrow but It could be never
4. write the code yourself..... Fine if you're an expert in that area but the learning curve is inclined shall we say.
or,
5. You could spam XDA daily with requests .
Personally I put this project to one side because my nexus 7 is out on loan to my brother after he decided to bathe his HTC OneX in Lucozade for an hour...
trevd said:
Well it WAS an easy hack, It's just a case of setting the configuration files up correctly. You get the N7 to advertize the Headset service and an Roberts your father brother as they say. I just about had it setup a couple of months back...... I want to control the full telephony service through the N7 show incoming calls and all the fun stuff.... As a first step I got the voice routing through the N7 Microphone through a handset and onto the caller. However I stopped there because that was using android 4.1.1 and I want to be using the latest build... Which is where your right out of luck because 4.2 onwards is a different beast,
Google decided to replace a tried and tested well documented fully implemented Bluetooth Stack with something that's not quite finished yet whose documentation is the source code. That's why there's no Low Energy stuff on Android yet..... It could and should have been implemented last year, anyway I digress. So the options are
1. Use a rom prior to 4.2 - In which case the Bluez is well documented and this sort of problem has been solved multiple times on the linux desktop and the same ideas can be applied to Android, Google is your Friend
2. put the old stack back in and work with that, There's patches that do that but they are all a bit brutal and would be a nightmare to maintain.,
3. Wait for the Missing Code to be added, which could be tomorrow but It could be never
4. write the code yourself..... Fine if you're an expert in that area but the learning curve is inclined shall we say.
or,
5. You could spam XDA daily with requests .
Personally I put this project to one side because my nexus 7 is out on loan to my brother after he decided to bathe his HTC OneX in Lucozade for an hour...
Click to expand...
Click to collapse
tnx for your answer.
but how can this be so hard?!
i used to do this with my laptop! :S