Trying to find a kitkat ROM that supports Voice dialling via Bluetooth on my note II sgh-i317m. If I role back to 4.3 it works fine (like DN3). I am currently testing CM11 and it does not work (unless somebody has a work around)
Most bluetooth functions work fine except voice dial. I hit voice commands on my Jabra and it does hear my commands. I also tried a Motorla bluetooth device and experienced the same.
Moved to Q&A.
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
FYI, over the last few days, I installed both Official AT&T / Samsung KitKat 4.4.2 and Ditto Note 3 v5.2 (based on 4.4.2) and they both properly support Bluetooth audio and microphone for voice command after a button press.
AT&T / Samsung Official:
Unfortunately comes with a version of Google Search (v.3.6) that provides the terrible Google Voice Dialer in response to a bluetooth button press, so if you were planning on using that, be prepared to root, move it from /system/ to /user/, uninstall, and then go find and install Google Search v.3.4.
S-Voice works fine, but you may need to switch your APN from "phone" to "nxtgenphone," if you haven't done so already. Else, S-voice may only work on wi-fi, not mobile data. Check out the thread on doing so here:
http://forum.xda-developers.com/note-3-att/general/psa-s-voice-stops-volte-markets-using-t2848929
Ditto Note 3 v5.2:
Comes with Google Search 3.4 which gives correct "Listening.." when bluetooth button pressed. Be sure to uncheck auto update in google play store until Google gets their crap figured out. Phone will flash as N7105, so download and use the build.prop for i317 from their extra files and turn on the telephony.lteOnCdmaDevice=1 setting. Set also ro.product.locale.language=en_US and ro.product.locale.region=US since you're an AT&T customer. You'll also need to add the nxtgenphone APN as above, I'm afraid. It's not rooted as it comes - use your recovery to flash the SuperSU binary of choice from your SD card after installation if you want root. It all works, though, and is my OS now.
rmzalbar said:
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
Click to expand...
Click to collapse
Related
We have a patent pending on an app suitable for Android, iPhone, etc. It requires manipulation of the outgoing audio stream during a telephone conversation.
If this is within your capability, and your team:
1. Has a proven technical capability in this area.
2. Can pass a background check.
3. Is willing to execute an NDA/NCA.
4. Is in the continental U.S.
Then we would like to talk with you. Please respond to notaguruatgmaildotcom to initiate a dialog.
Thanks!
Not to discourage you or anything, but a developer who meets those requirements is probably going to be asking for at least $150k a year.
Not only that, if your goal is to make changes to an audio stream before it goes over the air, it's probably not possible; certainly not for Windows Phone 7 or iPhone.
The way phone calls work on cell phones is that the mic is wired directly to the internal modem hardware, the sound doesn't go through the OS on its way over the air, so it can't be intercepted, modified and resent. That's how it's worked on the phones I've worked with. At best you will only be able to get a copy of the audio stream, and even that would take a jailbroken phone.
Or you could rewire the insides of your phone, but that would require another $150k engineer.
Thanks.
This is a single task, though as usual there must be ongoing support and evolution. I was hoping that an app company would respond, but that hasn't happened.
We have built prototypes using landline phones, with great success. In a cellphone, this could become a killer app with wide usage. But if the OS cannot gain access to the audio stream prior to the modem, that's a problem that can only be solved by incorporating the invention in hardware. A possibility, but it requires relationships above my pay grade.
Perhaps we need a consultant, not an app developer...
noguru said:
Perhaps we need a consultant, not an app developer...
Click to expand...
Click to collapse
Either way, be prepared to shell out cash, or stock options if your idea is really good.
hi,
well i'm against that policy, not able to post at developer threads under 10 posts, else I would have question that directly,...
I've tried several roms and ended at slim beam, first to 4.2.1 which states at stable but also tested the new one 4.2.2 build 2.5
actually i'm fine with the roms, also slim bean but I do have a 3 major issues with all of them which may be related to S3 and asop/cm:
1.) problem using my apple iphone earbuds (yes I'm a iphone user too)
sometimes after mute the microphone, it won't work after de-mute, keep on muted !
microphone not working after re-connecting earbud on a running call, sometimes no audio on earbuds too, sometimes audio even do not work for the whole device -> reboot etc,...
I've found several possible solutions, non of them has worked.
why android doesn't work with that kind of TRRS earbuds, are they incompatible from hardware point of view, do I need special ones which will work on S3.
2.) problem with direct dialing from calendar, not respecting RFC2806
i really need this very often to join conference calls, sometimes the host creates an conf call and including a number with pin as the location.
well almost every mobile os recognizes this and i'm able to direct dial in on selecting the string: iphone, win, even blackberry, but not android.
i know there might be additional apps which can handle this, but it should be implemented into core apps as this is a well known standard and specified in a RFC.
3.) not recognize AP with highest signal strengh within same SSID
it seems that android devices are not able to seamless switch over to different AP within a wifi network with same SSID.
if moving out of range of AP1 and into range of AP2, android devices for some reason are not able to switch to AP2 (with higher signal strengh), therefore it states at AP1 without beeing able to establish any connectivity (because AP1 out of range). as workaround users needs to disable/enable wifi ;-(
this is also something where I have to find a workaround in my current project (creating huge wifi network over europe), because market share of androids is that high and it still have this serious annoying bug.
thanks,
nean
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
10 post rule is there to protect developers from spam and users not knowing what belongs in a development thread and what belongs in Q&A
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
CNexus said:
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
Click to expand...
Click to collapse
thanks for the reply.
ad 1,2,3.) hmmm, is this working on googles stock os and eg on nexus?
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
nean24 said:
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
Click to expand...
Click to collapse
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
tazfanatic said:
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
Click to expand...
Click to collapse
thats correct, but it doesn't work on galaxy stock os either, that's why I've tried custom roms just to find out if its related to samsung stock rom or if its a general android behavior. well the outcome was that it works on aosp/cm a bit "better" (shorter timeout) but not seamless.
my intention is not about to blame anyone, just like to find out where I can adress this issue, or do I need to get in contact with google?
rgrds
I turned on my tablet the other night and on the screen was a system dialog box that said a new security profile (or something like that) was applied. It gave a number of the build but I can't remember what it was. I thought by clicking OK I would get some more info, but that was it. I checked for updates and there was nothing. I got no other information.
Anyone else see anything like this? I guess it's possible it was linked to some app I have installed. But the popup window definitely looked like a system framework box.
Edit: I guess I did find on the Security tab in the settings that it is set to Automatically install new security policies. So that would make sense, just wondering what might be included in this update?
I'm pretty sure that would be the same security profile updated to version 013 message that I saw as well. If I am to guess, we can thank Samsung Knox for that message.
<synicism>
Thank you samsung for applying a security profile update that I can't see the details of to a device I don't want Knox installed on in the first place.
</synicism>
<rant>
Wish they would put as much effort into getting an update released that fixes bluetooth keyboards. Or how about functional support for BT 4.0, like it suggests on the box? Yes, you can pass the buck to Google on that one, to which I reply, why was this tablet released on 4.3 when these bugs were known?
I generally love this tablet, but the defunct bluetooth combined with screen mirroring related reboots and the Knox warranty crap really has me waiting for someone else to release a non-crippled 10.1 high dpi tablet with an active digitizer so there is some incentive for Samsung to get its act together. Toshiba isn't even worth mention.
</end rant>
dpersuhn said:
I'm pretty sure that would be the same security profile updated to version 013 message that I saw as well. If I am to guess, we can thank Samsung Knox for that message.
<synicism>
Thank you samsung for applying a security profile update that I can't see the details of to a device I don't want Knox installed on in the first place.
</synicism>
<rant>
Wish they would put as much effort into getting an update released that fixes bluetooth keyboards. Or how about functional support for BT 4.0, like it suggests on the box? Yes, you can pass the buck to Google on that one, to which I reply, why was this tablet released on 4.3 when these bugs were known?
I generally love this tablet, but the defunct bluetooth combined with screen mirroring related reboots and the Knox warranty crap really has me waiting for someone else to release a non-crippled 10.1 high dpi tablet with an active digitizer so there is some incentive for Samsung to get its act together. Toshiba isn't even worth mention.
</end rant>
Click to expand...
Click to collapse
This message?
What's the harm? It's updating something already in place that you can't evaluate so why be up in arms about an update that you can't see to evaluate either? Samsung updates a bunch of stuff passively so it's kind of a trust exercise. Since passively doing bad things to people's s/w and h/w without their consent is a sure way for a publically held company to make the front pages of the news (in a financially damaging way) I'm trusting them until given a reason I shouldn't. Do you know what Google's changed security policy enforcement wise when they roll out updates to Android?
BT keyboard usage isn't broken. You need to disable the on-screen keyboard the first time you pair it. From then on the on-screen keyboard's automatically disabled when the BT keyboard is connected.
KNOX is benign when not in use with the exception of the warranty flag that detects the use of unknown ROMs being loaded on the device. I use KNOX on my N3 and N10.1-14 and like it. I also haven't had a single issue related to it.
And it's here to stay.
http://www.infoworld.com/d/mobile-t...-move-blackberry-users-android-and-ios-230343
Go do a little homework on android 4.3 and bluetooth keyboard issues, then I'll be glad to talk about constant disconnects, key repeats, etc. The note 2014 is even worse than other 4.3 tabs in the bluetooth dept. I have gone through 4 BT keyboards so far and each has disconnect and/or key repeat issues in a major way. This is in no way related to disabling the soft keyboard.
Like I said, it starts with google and some will lay the blame there and hold samsung harmless. I guess I have a higher expectation of quality control and since I bought a samsung product and have no direct relationship with google. Samsung selected this version of android for installation, so I think it is very reasonable to hold them accountable for the functional state of the resulting device.
As for Knox, I'd love it for managing enterprise devices as an MDM platform, but there is a reason MDM software has to be INSTALLED on other platforms. It's intrusive by its very nature. I'm not using this device in a corporate environment, it's my personal tablet. As such, knowing that Samsung has the reigns on a corporate MDM tool that wasn't advertised, I had no say in adding or removing, and also provides no visibility into what they consider an appropriate security policy, isn't exactly inspiring trust. You can trust them all you want, I don't see them as being any better than Apple at this point.
My ultimate point is simple. Samsung is wasting resources reinventing the MDM wheel and forcing it on everyone (whether they want it or not) while there are numerous functional issues with this tablet that aren't being addressed. I see that as a questionable ranking of priorities. If they're worried about device security, how about starting by keeping up with updates to The base android install.
---------- Post added at 02:53 PM ---------- Previous post was at 02:46 PM ----------
Also worth mentioning is the complete lack of release notes that go along with the system updates. Think about that for a minute. How do I, as a user, ever know from one update to the next what issues have been addressed, what functional changes have been made, or what areas might have been modified so I can make an educated decision regarding if/when to update?
Samsung has proven that they can and will remove things from one version to the next as they see fit. Why can't they actually tell people what to expect by putting out proper release notes like any respectable software developer would be expected to do? Samsung lacks the skill or capability to do what developers of $2 apps in the play store are capable of? Surely you jest...
I've been doing a ton of research and I want to know what the status is of using the Nexus 7 (2013) as a hands free device. I've seen some discussion about BlueZ, adding bluetooth profiles, using hands free kits, mic input from DACs, etc. but nothing really that recent. I'm hoping that there has been some development in this area with 5.1.1. The goal is to have the call audio go to the car speakers and maybe have an external mic for the audio in.
How are others doing it and what is the current accepted way to accomplish this? Can someone point me in the right direction? I'm starting to build my system and this is one of the last things I need to figure out.
I have the cellular version Nexus 7 if there's a way I can use that to send/place calls from the same number with a second SIM or something.
you can setup the nexus through auxiliary so that audio goes through the car speakers, and if your really picky about what kind of sounds go through your car speakers or the nexus speakers you can use an app like this https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=en
For making calls and such from a different device you should use an app like Mysms https://play.google.com/store/apps/details?id=com.mysms.android.sms&hl=en
It allows texting from any device using your phone by sending the info through wifi or bluetooth to your phone. It can also route calls from your phone to what ever device you want allowing you to answer with your tablet (with mysms this requires paid version, but there are likely other apps out there).
arolust said:
you can setup the nexus through auxiliary so that audio goes through the car speakers, and if your really picky about what kind of sounds go through your car speakers or the nexus speakers you can use an app like SoundAbout
For making calls and such from a different device you should use an app like Mysms
It allows texting from any device using your phone by sending the info through wifi or bluetooth to your phone. It can also route calls from your phone to what ever device you want allowing you to answer with your tablet (with mysms this requires paid version, but there are likely other apps out there).
Click to expand...
Click to collapse
The issue is that I'm replacing the head unit with the Nexus. I have Tablet talk which allows me to answer calls on m phone from the tablet, but the audio goes over the phone. I want to be able to answer the phone call on the tablet and have the tablet handle the audio. I've seen other threads about this and I've searched, but I haven't seen anything that are very recent. The best 'solution' I saw was implementing the BlueZ bluetooth stack to provide the required profiles, but I find their instructions confusing and it doesn't seem like anyone has attempted to get it working even though many people are looking for a solution to this.
Does anyone have any experience with implementing BlueZ on 5.1.1?
ok, your saying the app requires you to still use your phone to complete a phone call.
Using google voice setup and hangouts. Using this setup is the best I can think of. You can setup your current phone number I believe to work with google voice. Then just setup your phone to tether to your tablet.
Im fairly certain google hangouts can use your cellular service to place the calls and text, but if you have no service but have data/wifi it can use those, but im not 100% sure on that.
EDIT: I should clarify, google hangouts/voice works to make calls/texts/videocalls over wifi on any smart device without cell service. By using your own number your tablet will be able to make calls/texts/videocalls all from your number, all you need is data connection/wifi. I have not tried using hangouts over cell service without data, never had a need.
Troopster19 said:
The issue is that I'm replacing the head unit with the Nexus. I have Tablet talk which allows me to answer calls on m phone from the tablet, but the audio goes over the phone. I want to be able to answer the phone call on the tablet and have the tablet handle the audio. I've seen other threads about this and I've searched, but I haven't seen anything that are very recent. The best 'solution' I saw was implementing the BlueZ bluetooth stack to provide the required profiles, but I find their instructions confusing and it doesn't seem like anyone has attempted to get it working even though many people are looking for a solution to this.
Does anyone have any experience with implementing BlueZ on 5.1.1?
Click to expand...
Click to collapse
Did you find something. Sometimes I have the impression that some people just can't understand a simple English sentence, like arolust.
lung1 said:
Did you find something. Sometimes I have the impression that some people just can't understand a simple English sentence, like arolust.
Click to expand...
Click to collapse
Nah, I gave up - I got no support so I just broke down and got the MotorMouth 2.
But if someone were to figure it out I'd like to know the solution so I can have a single device act as my HU.
I'm working on a solution. Bluez lets you build AOSP for Nexus 7 2013 and it has HFP support. I will tell you if I did something. It really looks like no one is willing to help on this area. I searched a lot, but just peaces.
Troopster19 said:
Nah, I gave up - I got no support so I just broke down and got the MotorMouth 2.
But if someone were to figure it out I'd like to know the solution so I can have a single device act as my HU.
Click to expand...
Click to collapse
Subscribed
Sent from my Nexus 7 using Tapatalk
So, I've decided that right now there isn't any hardware out there that is enough of an improvement over the Note3 to get me to upgrade (will wait for SD820-based phones).
Unfortunately since T-Mobile has neglected this phone we are running a year-old version of Android, and thus are vulnerable to all of the fun widely-reported security holes uncovered since then.
From what I've been reading all AOSP-based ROMs seem to be dealing with NFC/sensor fusion issues (CM has open bugs for both issues).
My question right now is: is there anything available for the Note 3 that would allow it to have the latest security fixes without having to deal with other major issues like the ones I mentioned above?
I don't really even care about having 5.1, I just want my phone to be more secure.
I'm with you about new phones and actually dislike Note 5 (no SD, non removable battery etc. WTF Samsung, if I wanted iphone I would get one). As far as I know the stagefright is the only major issue on the system level, otherwise chrome bug for example should be fixed with chrome update and other stuff should be easy to avoid as long as normal precautions are followed (installing apps from Play store only for example). But I think even stagefright bug was little overblown. My understanding is Android has ASLR (random address space allocation) so buffer overflow bug is difficult to take advantage off, since the hackers don't know where in memory needed functions are located, so even with the bug, Note 3 should be relatively safe. I updated my wife's GS5 to latest Lollipop: she hates it, I don't like it much either , so not having latest operating software is not a problem for me. Bottom line I don't worry about it too much, I just scan my phone with antivirus and all it can find is that my phone is rooted, like I didn't know that already. I'm running stock, since I can't find custom ROM that has all functions enabled, like WIFI calling, NFC etc. There was some talk of monthly security updates for Android, like Windows have, but with Google, phone makers and carriers all involved, I doubt it will happen soon.