I found a site that says they figured out how to get a PS3 controller working on Android devices. I found out that it is not compatible with my device with my current ROM. According to the page i was reading it says that cyanogenmod is compatible because it uses the bluetooth protocol that the program needs. As far a I know cyanogenmod is not available on the EVO 3D. I was wondering if there is a way to put the bluetooth protocol that cyanogenmod uses into one of the custom roms we have available. I do not know anything about creating ROM's but i am attempting to learn what i can.
The site i found is at Dancing Pixel Studios. can not post a link yet sorry
Well your going to need to change your roms source and since we don't have sense source its impossible. Unless you know what files cm uses for this Bluetooth protocol it should be as simple as drag and drop
Sent from my PG86100 using XDA App
On cyanogenmod barebones wiki page i only find two apk's that deal with bluetooth. they are Bluetooth.apk and MediaUploader.apk. would the bluetooth protocols be in the bluetooth.apk?
push !!!!!!!!!!
duke8804 said:
I found a site that says they figured out how to get a PS3 controller working on Android devices. I found out that it is not compatible with my device with my current ROM. According to the page i was reading it says that cyanogenmod is compatible because it uses the bluetooth protocol that the program needs. As far a I know cyanogenmod is not available on the EVO 3D. I was wondering if there is a way to put the bluetooth protocol that cyanogenmod uses into one of the custom roms we have available. I do not know anything about creating ROM's but i am attempting to learn what i can.
The site i found is at Dancing Pixel Studios. can not post a link yet sorry
Click to expand...
Click to collapse
You need aosp with those hid profiles in order for that to work. Wait for an official build of cm7. That will be exciting, all 17 buttons are remapable
Remember, Remember, the 5th of November. Thanks for support!
Related
This is one feature that's surprisingly missing from Android. Is there any way to add it in or develop an app to do it?
Hell yes. I Miss that so much from my old win mo custom rom days!!!
Yes, it actually is supported in the source code, but it is disabled because there are some issues with it recognizing the voice command over BT, IIRC. I believe the line in the source is in BluetoothHeadset.java, or something like that. It is referenced in the bug filed against it on the Android tracker.
Perhaps some of the devs who build their custom ROMs from source can enable this in one of their future ROMs?
Developers? Can you chime in please?
Hello out there!
Well at least it sounds like out will be possible!
hi guys,
i just wanted to ask have anyone tried receiving calls from another phone in your gp5? i was just wondering i have a hp touchpad with webos and when its paired with my old phone it can receive the calls.
I was thinkin maybe if i can do that with my gp5 i can tuck away my old phone and receive calls with my gp5 when paired using bluetooth.
please let me know if anybody have any idea how get this done i know it requires certain service to enable this feature with bluetooth
The 4.0 and 5.0 do NOT support the bluetooth profile (HFP) Needed to be able to answer the calls of a paired bluetooth phone, the 3.6 does and I think the 4.2 might I just can't remember right now.
You could check out the custom ROM's for the 5.0 one of them may have added that functionality, but stock they will not.
4.2 does works like a charm. Just like my tp
Sent from my YP-GI1 using XDA
Well, it is unreal to answer a call? if you have not a dial, isn't it? So, galaxy player 4 and 5 HAVE NOT a dial (a phone app), maybe, in some custom ROMs... And they also have not (HFP) and you could not use them as hands-free...
server60 said:
Well, it is unreal to answer a call? if you have not a dial, isn't it? So, galaxy player 4 and 5 HAVE NOT a dial (a phone app), maybe, in some custom ROMs... And they also have not (HFP) and you could not use them as hands-free...
Click to expand...
Click to collapse
No, they have a dailer, they lack support of the needed bluetooth profiles, It was one of those weird things samsung did.
attn: ICS and custom roms user
any body running custom ics roms here? please feedback i need this badly it really sucks limiting the potential of this device i agree this might just be be something samsung disabled and might just work with custom roms with full functionality
aben.dc said:
any body running custom ics roms here? please feedback i need this badly it really sucks limiting the potential of this device i agree this might just be be something samsung disabled and might just work with custom roms with full functionality
Click to expand...
Click to collapse
Unlikely to see it in any of the CM9 based ICS releases as bluetooth doesn't even work in most of them.
Right. Calling custom fw users based on gingerbread kindly check if this feature exist on your gp5..thanks
Sent from my YP-G70 using XDA
i found a thread in htc flyer to enable hands free profile
http://forum.xda-developers.com/showthread.php?t=1185688
Using root explorer or your favorite text editor edit the build.prop file under /system/build.prop and edit the following lines:
Code:
ro.ril.reject.cs.ss.enabled=0
ro.ril.reject.mo.ussd.enabled=0
ro.phone.function=1
To enable Bt Headset profile change the following:
Code:
ro.bt.profiles = 4270403
service.brcm.bt.ag_supported = 1
Click to expand...
Click to collapse
thinking it might work with sgp 5.0 i tried opening my build.prop and cant find any lines like above
sadly it seems like nobody is after this feature but me
edit: added build.prop file and renamed to .txt
I'm very much interested in this feature and i'm sure there are people out there who care about it as well. I really would love to be able to use GP5 with my 10' tablet to answer and make calls though it.
aben.dc said:
i found a thread in htc flyer to enable hands free profile
http://forum.xda-developers.com/showthread.php?t=1185688
thinking it might work with sgp 5.0 i tried opening my build.prop and cant find any lines like above
sadly it seems like nobody is after this feature but me
edit: added build.prop file and renamed to .txt
Click to expand...
Click to collapse
I would love this feature! So did adding those lines to build.prop do anything?
Sent using Tapatalk
Okay, I tried adding the line in my build.prop, but it still fails to connect. Not surprised, but disappointed all the same.
Sent using Tapatalk
Thanks for trying. I got an idea based on the previous posts the 3.6 player has this feature I was wondering if the 3.6 has the identical chipset as ours provided that the its coming from the same rom version we can dump some of their core files that is controlling the bt chipset and port it to our device
Sent from my YP-G70 using xda app-developers app
i'm planning to post a request in the development forum, asking the developers to incorporate this feature into one of the rooms
I already asked the 4.0 devs. What we need is a 3.6 dump, so we can get what files we need.
Sent using Tapatalk
a dump? arent official roms available for download? why can't the necessary code be taken from a rom?
both 4.2 and 3.6 have this feature enabled, so it can be imported from any of these devices. I think it should be trivial - because the devices use the same components, adopting features from one into another should be almost as easy as cutting and pasting the code or a library or whatever they have in android.
Hi guys, since my 3.6 isn't rooted I'm not sure I can dump every file, but I can extract the ones which I have read access. You can also download all the source here
Mars11_ said:
Hi guys, since my 3.6 isn't rooted I'm not sure I can dump every file, but I can extract the ones which I have read access. You can also download all the source here
Click to expand...
Click to collapse
Wow, thanks for the link, mate. I will forward you offer to the devs. Btw i've started a new thread dedicated to this in the development section -> http://forum.xda-developers.com/showthread.php?t=1763496
double post
Dear folks,
I have a trusty Dell Streak 5, which I appreciate much, buuuuuut..... I keep getting this error message when trying to load a DSLR controller: "Your Android device is not compatible with Android's USB host API. A newer firmware for your device MAY fix the problem"....
I am currently running Longhorn 2.91 (Android version 2.3.7), Kernal version 2.6.35.14-DSC-Team_Phoenix [email protected] #346, Baseband Version GAUSB1A136000-US.
Are there any fixes for this issue, do I need to change the ROM or what other options have I?
Also, on a side note request, is there a way to change the LCD resolution, everything is a bit too small and unreadable?
Thanks very much!
~J:cyclops:
What's the exact app? If it's doing what I think it's doing, you need to be using Android 3.0 or newer.
If it's using the android usb accessory api, that was introduced in either 3.0 or 3.1, 2.x predates it.
If it's actually trying to become a usb host, it's supported in hardware but it's not terribly reliable in all our current roms.
As for the font sizes, you'll want to read up on ro.sf.lcd_density, the S5 uses 160 while most devices use 240.
Trying to figure this suckah out!
Hello TheManii,
The exact app is this one: DSLR Controller (BETA) 0.94.1 (I cannot, as of yet, post the link).....
Is there a DLSR app that I can use for this ROM pkg? So frustrating indeed!! Or perhaps a workaround?
Is there an app or an add-on for S5 for the LCD?
Thanks much!
~J:highfive:
jayguruson said:
Hello TheManii,
The exact app is this one: DSLR Controller (BETA) 0.94.1 (I cannot, as of yet, post the link).....
Is there a DLSR app that I can use for this ROM pkg? So frustrating indeed!! Or perhaps a workaround?
Is there an app or an add-on for S5 for the LCD?
Thanks much!
~J:highfive:
Click to expand...
Click to collapse
is is easy, install the DSC Rom , there you will have a configuration tool called DSConfig, the LCD settings are there too.
DSLR Controller (BETA) - Play Market seems to require your device either support usb hosting or usb accessory mode.
I dont know if DSC supports hosting, as I dont use dsc. But like previously stated usb accessory is for android 3.x and newer.
You might be able to get assitance from n0p to get it supported if you're simply using hosting, though dont expect any type of quick fix, it may take a fair amount of work if it works at all.
You could try using AOSP/ICS as it's new enough to 'support' usb accessory mode, though weither or not our rom+kernel has it working is an entirely different story.
tl;dr: the S5 is a bad canidate for this as it has very weak usb support for connecting other devices. If you plan on using DSLR controller heavily you're definitely better off with a different device.
yes, DSC supports usb hosting fully.
Use a sixaxis pairing tool............
And connect a ps3 controller
Its good...... Works fine for me......
All it needs is a root.....(which u shoul have)..:thumbup:
Sent from my Dell Streak using xda premium
The saga continues?!
Thanks for the various replies. I am trying to figure out the best most updated ROM to do this, to use this DELL Streak 5 as a DSLR external monitor. I am currently using Longhorn 2.91 but that, apparently, does not offer the support that I seek. It also goes and stays in landscape mode during calls which I cannot seem to change... Dang ROMS never all perfect... Hahaha!! I may have to just suck it up and get another gadget but I like the idea of having one gadget that does it all, ya know? I cannot stand having a ton of stuff! If you good folks have suggestions regarding the most stable, up-to-date ROM that offers USB controller options, that would be superb!!
Thanks much and have a great weekend!
Hi,
As you may know Sony has not updated its bt libs even for its own bt devices such as mw600. Hence at least the device I mentioned and own does not show song name or caller ID on its screen. This problem is fixed only and only in CyanogenMod Android ROMs.
There is a bug report discussion here about one version of CyanogenMod Android ROM which did not have the proper libraries. The developer has found the file causing the issue and has posted it and everybody confirms the fix.
Well, I tested putting the file in respective place in a GB rom but it did not work. Most probably a different file is needed.
Can someone help me with it?
Thread on CM
Here is the link of the thread I started on CM official forum to get an answer from a dev directly, hopefully
Links of related posts on other thread
I had a talk with two valued devs on another thread. Here are the links to the posts:
http://forum.xda-developers.com/showpost.php?p=31302309&postcount=416
http://forum.xda-developers.com/showpost.php?p=31302499&postcount=417
http://forum.xda-developers.com/showpost.php?p=31303125&postcount=420
http://forum.xda-developers.com/showpost.php?p=31303537&postcount=421
http://forum.xda-developers.com/showpost.php?p=31303819&postcount=424
http://forum.xda-developers.com/showpost.php?p=31305983&postcount=432
Sony Support Thread
With so many devs here and on CM website, still no answer! I made a thread on Sony Mobile website here.
Greight said:
With so many devs here and on CM website, still no answer! I made a thread on Sony Mobile website here.
Click to expand...
Click to collapse
Sorry I can't help you bro, but all I'm here to say is good luck getting help from Sony Mobile Forums, they are so useless over there. I hope you find your answer.
evilbarcode said:
Sorry I can't help you bro, but all I'm here to say is good luck getting help from Sony Mobile Forums, they are so useless over there. I hope you find your answer.
Click to expand...
Click to collapse
Well, you know I was going to add the same sentences at the end of my last post but somehow I changed my mind because I could get this simple (for devs of course) answer NOwhere. Still hopeful...
Sony's Support Reply
Well, I recommned you go to Sony support site to see the whole answer, but anyway the answer confirms what I thought:
As far as I'm aware it's due to a lack of a certain Bluetooth profile this function isn't available in some phone's.
Click to expand...
Click to collapse
Come on devs! Any ideas?
New Discussion Found
Well, I found another thread here talking somehow about this problem. Here are some highlights of the thread;
The MW600 will not show up Track Title or for that matter any other information when used with Android. Reason being, Android uses Bluetooth profile AVRCP v1.0. However, in order to get extra information (metadata) like Track Title, Caller Name, etc. you will need AVRCP v1.3 and above; which none of the Android version has...
Click to expand...
Click to collapse
It works on CM7 as CM7 supports AVCRP 1.3
Click to expand...
Click to collapse
They've implemented it on CyanogenMod 7 (CM7) officially as of version 7.1.0, according to the changelog. Whether it actually works or not may depend on the particular phone and if it's been tested.
Also, it only works with the stock CM music player (so far). I'm currently using ThGoCm v3.0, and... it doesn't come with the stock player.
According to this thread (http://forum.xda-developers.com/showthread.php?p=18211506&highlight=avrcp#post18211506), it's at least partially working on FreeXperia CM7.2.0 (http://forum.xda-developers.com/showthread.php?t=911364)! That was for version FXP030 though, and it's currently at FXP046. I'll probably try it this weekend.
AVRCP stands for "Audio/Video Remote Control Profile". To put it simply, AVRCP is the part of Bluetooth that lets you stream music. Only version 1.3 and higher can show track info, and stock Android has been using version 1.0.
Click to expand...
Click to collapse
So this AVRCP thing is the reason why I get no proper display of the songs' titles on my bluetooth device because the phone does not communicate with it completely.
Now please somebody find a solution to update AVRCP on all roms, as it is on CM.
As the thread says I'm using Task's 10.5 AOKP build on my i777. I'm trying to listen to music in my car using the official Samsung car dock and Google Play Music. I've tried using the Settings->Device options->Dock->Use Dock USB Audio checked or unchecked but it didn't make a difference. Settings->System->Dock->Audio is always grayed out for me, even when docked.
I've posted in Task's thread but I expect it to get burried
Has anyone used any AOKP ICS/Jellybean ROM with a dock and gotten the audio to go out the USB port?
Thanks,
GFunk
This issue is not specific to the Galaxy S2 nor Task's ROMs, it seems this is common with ALL AOKP/AOSP/CM ROMs I don't know the specifics but I would guess that since these ROMs are based on original android source code and not off of ROMs written for the phone, there is no Samsung coding written in for the docks.
I have an S3 and would really like to get dock support for it too, but I'm not sure the mentioned ROMs will ever have support for it. You could always request it in the Rootwiki's (home of AOKP) website and see what they say.
Thanks, Risingsunn. I was starting to gather it was an AOSP issue. I was hoping it'd be some easy xml or sql setting that could be set from false to true or something similar. But I've been scouring with root explorer and haven't found anything promising. If it's ROM-based as opposed to Kernel-based I would expect it to be a setting rather than baked into a launcher or music app.
It's just interesting that there's a Dock Audio setting in the device options, and my phone goes into "Car Mode" when docked...but the audio never goes to the dock via the USB port. So I'm convincing myself it's a setting somewhere and will continue to dig .
Edit: Looks like they were playing with this issue over at CM:
https://github.com/CyanogenMod/android_frameworks_base/blob/e91a2373758b2302370c826b56cc022d2eb04b5d/services/java/com/android/server/WiredAccessoryObserver.java
If you search for "dock" you can run across a few instances where extra code was apparently added to be able to use dock audio on Samsung devices. I've never tried a CM ROM to see if this is actually implemented correctly, have you? You mentioned CM in your post, that's why I ask.
AOKP Dock Issues
Risingsunn said:
This issue is not specific to the Galaxy S2 nor Task's ROMs, it seems this is common with ALL AOKP/AOSP/CM ROMs I don't know the specifics but I would guess that since these ROMs are based on original android source code and not off of ROMs written for the phone, there is no Samsung coding written in for the docks.
I have an S3 and would really like to get dock support for it too, but I'm not sure the mentioned ROMs will ever have support for it. You could always request it in the Rootwiki's (home of AOKP) website and see what they say.
Click to expand...
Click to collapse
...AFAIK this is an issue only with AOKP based ROMs. :crying:
AOSP based ones don't have this problem; I have SlimRoms since version 2.7.0 (AOSP based) perfectly working with my docks...
Hope this clarifies the matter...