[Q] Bluetooth Protocol Help - Captivate Q&A, Help & Troubleshooting

So there is a program called sixaxis ( http://www.dancingpixelstudios.com/index.html ) made by dancing pixel studios. It allows the pairing of android devices with ps3 controllers. Apparently, it is incompatible with all HaichTC devices and some newer samsung devices, ours in particular.
The supposed reason for this is due to incompatible bluetooth protocol. Oddly enough, the website states that the Cyanogenmod ROM carries the appropriate bluetooth protocols.
Is anyone familiar with bluetooth enough that they could help me down the rabbit hole to solving this problem?

Security Warning
My IE9 pops red when accessing the URL posted above. Microsoft has labeled above URL as dangerous. This is the first time I saw IE pop this thing out.
The site might have been hacked with malicious code injected.
As for OP's question, you need two parts:
1. Specific BT protocol support required by the PS3 controller. Samsung are notorious for shipping only the bare mininum BT protocols. You need to find a custom ROM that specifically supports the protocol.
2. Kernel driver for PS3 controller. It's not part of the standard feature delivered by official ROMs.
All in all, if you want to use console controllers, there are custom ROMs out there for that purpose.

Related

Bluetooth controllers?

Are there any bluetooth controllers currently compatible with the SGS?
I know I can use the Wii controller, but I don't have a Wii, so that idea probably isn't best.
Thanks in advance.
not really an answer to your post, but...presumably either way you'd also have to buy a Bluetooth controller so it's probably just as easy to pick up a Wii one?
I would prefer something a little more portable and cheaper if at all possible
From what i've seen, the Wiimote is not working on the i9000 yet.
Correct me if i'm wrong please. (And seriously, this time i want to be wrong)
If you can get a Wii controller working, shout me - I've been trying since I got my Galaxy with every different firmware/update combination - it's a no go at the moment.
Ryan Frawley replied to an email I sent saying it's down to samsung's bluetooth drivers being modified as compared to the standard Android drivers.
As I was writing this post, I checked my mail to look up Ryan's reply, and found a reply from Samsung to a mail I sent a few days ago (last friday I think). I will post the conversation in it's entirety here, I hope the employees at Samsung do not mind, as I do quote this without permission:
Hello, and thank you for your time.
I have a question regarding connection of HID devices and, in particular, the WiiMote (Nintendo) to the phone, through applications available through Google Market.
Applications (such as 'Wii Controller IME' from Ryan Frawley) using bluetooth to cennect to certain HID devices appear to be unable to connect to the bluetooth drivers (the application fails to connect, and does not appear to be able to get as far as searching for the device).
Are there any plans to update/fix the bluetooth drivers to address this issue in upcoming firmware updates?
Does the upcoming Android 2.2 (FroYo) update address the issue, and should we so wait until the release of the 2.2 update?
Click to expand...
Click to collapse
Reply:
With regard to youremail, these are questions that need to be
redirected to Android, as we do not make the applications that connect
to the Wii-mote, and also have no information on the Froyo upgrade.
I hope this has been of someassistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-
reference number.
Kind Regards
Click to expand...
Click to collapse
My reply:
hank you for your reply to ref# XXXXXXXXXX.
I will try and contact Android customer service to expand on the query, but I have some more questions I would like to ask to clarify the situation:
- you state that Android is responsible for the applications which connect to the Wii remote. However, the Android version which is installed on the Galaxy will have been researched and developed by Samsung's own technicians.
The applications on the market are capable of connecting to the Wii remotes (and other bluetooth devices) on other Android devices - yet all applications have issues connecting through the bluetooth drivers on the Galaxy. Indeed, I have yet to find even a standard HID device which connects to the Galaxy successfully.
By it's very nature, Android is open sourced - anyone with technical know how should be able to view the internal workings of the operating system and (often in an attempt to fix problems like this) edit the underlying files.
It appears that the bluetooth drivers (along with all hardware drivers on the Galaxy), as supplied by Samsung are not open sourced. Nor do they adhere to the standards which applications on the Android market are able to connect to bluetooth.
This in turn points at problems with the Galaxy, and/or it's bluetooth drivers, which are, of course, designed and supplied by Samsung.
Please, if possible, can this issue be escalated to a technical team - I understand the issues of getting a problem raised within a multinational company; I work for one myself and deal with such issues on a daily basis.
I would greatly appreciate your help in dealiing with this issue, and getting help in raising it to the correct team/department to have the issue resolved, if it is at all possible.
Again, thank you for your time,
Click to expand...
Click to collapse
As usual, I don't expect much to come from this to be honest - my previous experience with this kind of query tells me that it'll get shoved under the carpet relatively quickly.
We'll probably be waiting until a proper Cyanogen ROM turns up, or someone gets either Ryan Frawley to patch up the application side (though I'd much rather the bluetooth drivers were standardised to begin with).
PS: Anyone tried a zeemote, mini bluetooth keyboard yet? I'm tempted to throw £30 or so on a keyboard/zeemote combo but I would like to know if it's something that will work out of the box or not.
I feel the need to bump this thread, since I'm so in need of this functionality.
Well, I got an update from Samsung. This sounds very promising, I hope they follow through with what they've told me:
Thank you for contacting Samsung Electronics regarding your mobile phone.
Please accept our sincere apologies for the delay in responding to your enquiry.
With regard to your email, this issue has been passed to our development team and has been raised with Head
Office as well. There is a solution in development and will be forthcoming shortly.
Please keep checking the website for updates on this issue.
I hope this has been of some assistance to you.
Click to expand...
Click to collapse
Raised with Head Office? Hmmm...
What about connecting a PS3 official keypad (the one you attach to the PS3 controller) to the SGS? It would be useful to use in games like Quake 2 and 3, that need a physical keyboard to play. Has anyone done this? I have tried and have been unable to get it working.
The SGS can see the keypad, can pair, asks for the password but fails to connect.
AlexandreT said:
What about connecting a PS3 official keypad (the one you attach to the PS3 controller) to the SGS? It would be useful to use in games like Quake 2 and 3, that need a physical keyboard to play. Has anyone done this? I have tried and have been unable to get it working.
The SGS can see the keypad, can pair, asks for the password but fails to connect.
Click to expand...
Click to collapse
Did you try this? www.appbrain.com/app/com.mymobilegear
AlexandreT said:
What about connecting a PS3 official keypad (the one you attach to the PS3 controller) to the SGS? It would be useful to use in games like Quake 2 and 3, that need a physical keyboard to play. Has anyone done this? I have tried and have been unable to get it working.
The SGS can see the keypad, can pair, asks for the password but fails to connect.
Click to expand...
Click to collapse
That's the problem with most devices - the SGS will see the device and it's MAC address when scanning, but won't connect. Usually "0000" gives a very quick refusal, where anything else (the only way I've found to enter a blank PIN is to enter a digit then delete it) gives a rather long wait with "Connecting" then a message telling you it failed to connect.
Most 3rd party apps don't work either, though I've had success with the GamePro app NZTechFreak used - it's the only app I've found on the SGS up to now that does work with bluetooth. I'm pretty confident KeyPro from the same company would work, but I don't have a compatible keyboard to test.
Up to now, i've tried:
Wii remote/classic controller (original) - SGS sees controller, will not pair
Bluetooth "I-Tom" keyboard (ebay) - Despite coming with android drivers, does not work. Same symptoms as other controllers, third party app does not detect nor connect to controller.
Datel Wii Classic Controller - same as Wii controller
Zeemote - Works with GamePro drivers. Zeemote does not pair directly with SGS, it's all handled through the GamePro IME drivers/settings
I'd like to see if a PS3 controller pairs successfully, but from what you've said I doubt it very much
e: The app in the post above only has support for some very specific keyboards. By all means try it, I tried each one on my itom keyboard but nothing worked.
SquidgyB said:
Well, I got an update from Samsung. This sounds very promising, I hope they follow through with what they've told me:
Raised with Head Office? Hmmm...
Click to expand...
Click to collapse
Have you got any update on this?
I am also wondering. I have been trying to pair a bluetooth mouse with no luck.
ei0haro said:
Have you got any update on this?
Click to expand...
Click to collapse
Heh - nope. 'Fraid not.
[BUMP!]
Samsung has released 2.2 but still does not work.
Samsung has also released the source for many of their phones.
http ://opensource.samsung.com
It would be great to get this fixed.
Jim
jim0watters said:
[BUMP!]
Samsung has released 2.2 but still does not work.
Samsung has also released the source for many of their phones.
http ://opensource.samsung.com
It would be great to get this fixed.
Jim
Click to expand...
Click to collapse
Bumpity bump bump bump
apparantly latest cyanogenmod7 for SGS works with wiimote
I might start using it after the cameras are fully working and a few other bugs fixed.
oswade said:
apparantly latest cyanogenmod7 for SGS works with wiimote
I might start using it after the cameras are fully working and a few other bugs fixed.
Click to expand...
Click to collapse
Yahh it does work ;D I wonder if there's a way we can build a samsung kernel with the bluetooth modules from cyanogenmod? Hopefully the cameras are fixed soon this is a showstopper bug for me atm

[Q] usb keyboard with case

I purchased the case with imbedded keyboard and initially the kb worked great. However, now I can't get it to function at all. Have tried playing around with settings etc., but no go. Anyone having success or probs with this keyboard? Thanks,
ooorah
Have you tried restarting the A7? (fully power down, not just lock the screen)
Coonecting a keyboard...
ooorah said:
I purchased the case with imbedded keyboard and initially the kb worked great. However, now I can't get it to function at all. Have tried playing around with settings etc., but no go. Anyone having success or probs with this keyboard? Thanks,
ooorah
Click to expand...
Click to collapse
I read the users manual (available on-line) and they clearly state that the USB port only has support for USB flash drives.
2.3 Connecting USB Devices
With the USB 2.0 host port, you can connect USB flash drives to your
Tablet to access external files. The Tablet supports drives up to 64GB in
size. Please note that some older USB 1.1 devices may have
compatibility issues.
The Tablet supports flash memory drives only; it does not support other
mechanical drives
The other way to connect a keyboard is via bluetooth. Again, the A7+ supports limited Bluetooth connectivity:
Bluetooth Device Requirements
The A7+ Tablet officially supports only A2DP Bluetooth devices with
stereo audio capability. Mono devices such as cell phone speakers and
earpieces are not compatible.
Important Note: The A7+ does have limited Bluetooth compatibility with
certain Mac computers and other assorted peripheral devices, but it does
not support printers, scanners, bar code readers or most other peripheral
devices even though the Tablet will detect and “pair” with such devices.
The necessary “connection” can only be made with proper drivers. Until
hardware manufacturers of these devices create the necessary drivers to
support both Android and the Tegra
This information is from the latest version of the owners manual dated March 2012. I'm afraid that you're out of luck unless you upgrade the operating system.

Airtame - I'd like this from my Chromecast!

Airtame is a new HDMI dongle that promises to allow you to display anything from your devices...
Details here: http://www.indiegogo.com/projects/airtame-wireless-hdmi-for-everyone--2
I was one of the early Chromecast buyers, successfully able to root and now running a number of the utilities found in this forum. But I still want to be able to simply cast anything I see on my pc or android phone to my TV. This new crowd-sourced device promises to do that, and more. Take a look at the link to see all the cool things they've planned. They started out requesting $160k, but have raised nearly $1M. With each successive goal completion, they've added a stretch goal and have achieved nearly every one. I think the key to its success is the ability to display just about any content you want.
Is there a way to do the same with our Chromecasts? I see the only thing holding it back at the moment is content. The devs here have been doing wondrous work bringing in content and more will be made available. Can we make Chromecast open to all content?
Oh, and they won the Engadget award for the "Best Startup of CES 2014"!
Admins - Please feel free to move/delete if you feel this is inappropriate.
Android screen mirroring seems to be on the way but it will require either Google or an OEM (not third party developer) to implement it, probably because of security concerns (not to mention DRM/copyright concerns).
https://plus.google.com/110558071969009568835/posts/ch57ZKvqpYb
Meanwhile Koush is continuing to work on his own alternative for other targets.
Meh!
Only supports PC's etc. DOES NOT and by the sound of it WILL NOT support Android other than as a remote.
Miracast already does this and all this seems to do is remove the proprietary Miracast Wireless part of it...
CCast could do this already if someone just made an app for it and got it added to the whitelist.
I'm actually working on getting the Airtame software running on the Chromecast. The software, its library and the protocol will be open source, so don't worry so much about hardware support just yet. Just stick around and see what the community will come up with. Disclosure: I'm working at the same office as the Airtame team.
Right now my problem is getting the Chromecast to a hackable state. The ones I have are all updated past the fixed boot loader, so I need to find a new vector. Last night I tried to solder probes to the I/O pins of the NAND chip itself to dump the flash using an Arduino and its super slow serial connection -- better than nothing at least. I need to find some thinner wire though; the stuff I used was 20-something AWG. Will give it another go next weekend.
Looking forward to it jchillerup
jchillerup said:
I need to find some thinner wire though; the stuff I used was 20-something AWG. Will give it another go next weekend.
Click to expand...
Click to collapse
Wire-wrapping wire (Kynar, 30+AWG) is your friend, though that stuff will break if you sneeze. Forceps and magnifying glass are also your friend.
And if you haven't already, sign up to be a developer so you can get your Chromecast whitelisted. That's the "proper" way to do mainstream Chromecast development.
MadBob said:
Meh!
Only supports PC's etc. DOES NOT and by the sound of it WILL NOT support Android other than as a remote.
Click to expand...
Click to collapse
Did you read the fundraising targets? It hit a million, so there will be android and iOS support.
Sent from my GT-N7100 using xda app-developers app
Sound awesome
Sent from my SCH-I605 using Tapatalk
Looks interesting. But in the faq it states that the ability to stream from an Android or iOS device is technically possible but access to specialized hardware is restricted by the vendors, thereby needing root or jailbreak to work. Which they also say they will not support. That's their words, so it looks like the road map is only for a remote or possibly casting a screen to the mobile device.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I like the way Airtame is heading but the price is overkill. Chromecast + Avia ($2.99)=$38 is already have and can do what airtame can except the optional ethernet port.
SPH-L720_!
ntajlis said:
I like the way Airtame is heading but the price is overkill. Chromecast + Avia ($2.99)=$38 is already have and can do what airtame can except the optional ethernet port.
SPH-L720_!
Click to expand...
Click to collapse
Hard to get the price down to Chromecast level when you can't order millions at once, and there is not a big search engine with ad revenue backing the financial losses on a 35$ device....
siratfus said:
Did you read the fundraising targets? It hit a million, so there will be android and iOS support.
Click to expand...
Click to collapse
Well they have raised the Funds now the hard part starts...Actually manufacturing them! LOL
atiti said:
Hard to get the price down to Chromecast level when you can't order millions at once, and there is not a big search engine with ad revenue backing the financial losses on a 35$ device....
Click to expand...
Click to collapse
Google probably isn't even making a penny off the CCast sales either....
This device is all about the DIAL protocol whose patents are co-owned by Google and Netflix.
It is meant mostly as a way of expanding the customer base for their content products to those who do not have a Smart TV or other streambox connected to their TVs.
It is far simpler to create a standard method for streaming to remote devices and creating a device to do that than it is to get the 5-10 TV Manufacturers to adopt a protocol standard that has not already been established in the Market.
This device seems to be a hybrid CCast/Miracast. The Main difference is that it doesn't use Player Apps as much as it does Mirroring. WHich is good in cases where Mirroring is desirable but it depends on the streaming device to do most of the work (aka BATTERY KILLER!)
CCast should be able to do everything this device claims to do if only Google would open up the Whitelist or create the apps for Mirroring.
Mirroring makes sense in some situations but not all. And unless this device adds some of the DIAL capability Chromecast has to play content without requiring the initiating device to do most of the work this seems a bit like a Miracast killer but still won't be as useful as the Chromecast is, Knowing what we know it is capable of doing if only Google would let it!
Just to add I would describe the three methods like this...
Miracast - Mirror via Wireless Radio ONLY!
Airtame - MIrror via IP
Chromecast - Mirror via Wired or Wireless (such as the way GoogleCast works), PLUS the ability to play remote content without killing your battery.
All Google really needs to do to beat the other two contenders is to more fully support Mirroring on more Platforms than just the desktop or add the capability to add the CCast as a display device for PC, Tablets and Phone.
If it does that then the others will be forced to act more like Chromecasts to sell.
Asphyx said:
All Google really needs to do to beat the other two contenders is to more fully support Mirroring on more Platforms than just the desktop or add the capability to add the CCast as a display device for PC, Tablets and Phone.
Click to expand...
Click to collapse
Now, I'm obviously biased but I just want to make one point clear: There is a difference between Airtame and the Chromecast in that one is completely open source and hackable while the other one isn't. Want root? You got it. Moreover, the Airtame protocol can be implemented by whoever wants to move imagery and metadata from one device to another with low latency.
The Airtame team acknowledges the fact that they're not just selling a commodity device; they're selling a tiny computer to people and they're encouraging the community to hack around with it. If we're just looking at differences in current offerings we're completely disregarding a (potential) community around this thing.
jchillerup said:
Now, I'm obviously biased but I just want to make one point clear: There is a difference between Airtame and the Chromecast in that one is completely open source and hackable while the other one isn't. Want root? You got it. Moreover, the Airtame protocol can be implemented by whoever wants to move imagery and metadata from one device to another with low latency.
The Airtame team acknowledges the fact that they're not just selling a commodity device; they're selling a tiny computer to people and they're encouraging the community to hack around with it. If we're just looking at differences in current offerings we're completely disregarding a (potential) community around this thing.
Click to expand...
Click to collapse
I understand but the fact it can be rooted will not make it play content without requiring a device to stay connected to it.
If they add DIAL support so you can launch a content and then go play a game on the device that launched it they have a shot...
But from what I have seen and heard of from this device, it is merely a Mirroring Dongle that doesn't require some proprietary wireless protocol to do it's Mirroring like Miracast does!
So it will Mirror in a similar way that the CCast does, but not do the other stuff CCast does.
And if Mirroring is all you want it's much better than Miracast!
Not Knocking the product at all just pointing out it is a different beast that CCast and not even trying to do some of what the CCast can do...
This Airtame sounds just like Ouya when they promise the device to be hackable and rooted. Then it happens. Look what happens to the Ouya.
SPH-L720_!
What's annoying with all these devices is that they require your tablet or phone to use a certain OS number. Is the Airtame any different?
I've been searching for a mirroring device for the Sony Tablet S, and nothing is compatible with the OS version I currently have. The damn thing doesn't even allow micro usb to HDMI cables. Miracast, tronsmart, etc.. "S" stands for SUCK in Sony Tablet S. It has the latest updates too. So there is nothing more I can do other than wait for Sony, and I don't think they'll support this tablet anymore. It has a stupid "throwing" feature for DLNA, but I need to mirror streaming apps and sites.
siratfus said:
What's annoying with all these devices is that they require your tablet or phone to use a certain OS number. Is the Airtame any different?
I've been searching for a mirroring device for the Sony Tablet S, and nothing is compatible with the OS version I currently have. The damn thing doesn't even allow micro usb to HDMI cables. Miracast, tronsmart, etc.. "S" stands for SUCK in Sony Tablet S. It has the latest updates too. So there is nothing more I can do other than wait for Sony, and I don't think they'll support this tablet anymore. It has a stupid "throwing" feature for DLNA, but I need to mirror streaming apps and sites.
Click to expand...
Click to collapse
Well it requires certain OS' because it requires a WiFi implementation that is relatively new and not supported by older OS'.
But for the Record I don't believe the Airtame suffers from that problem at all. I believe it works closer to the CCast in that it connects to the Wireless Router and you stream over IP which does not require any specialized WiFi support.
It is not making a direct Radio to Radio connection.
Miracast does.
My biggest desire is straight-up mirroring. Whatever I display on my PC to a tv/projector. I like the idea of CCast having competition. Maybe this will entice Google to open it up a bit more if people have alternatives.
For those that commented the cost was too high, just think about what you're getting: dual core cpu, b/g/n wireless, I/O, ram... and open. pretty sweet for the cost.
But it will not compare to the CCast as G is playing the long game - they'll know anything you're looking at/casting and target you with promotions and use your aggregated data. Now, couple that with what's going to happen with the Nest thermostat/smoke detector. They'll know when you're home, where you live, your daily home/away habits, when you rise, when you sleep... I want options that aren't tied into G. Just wait until they offer a Google 'Fridge that inventories what you purchase and makes a shopping list for you and a Google ODB-II dongle that plugs into your car and maps out your gas mileage, frequent trips, etc and projects it to your Android Phone, while they collect the data.
Yes, they are out to know everything... and it starts at home. Like I said, I want options.
So this still won't support Android? I think on the airtame website the lead mentioned this is because "we need Google or Apple to open up". But couldn't they support an airtime android app to use only rooted, and with CyanogenMod (or other aftermarket ROM)?
Also, plain mirroring is boring (though still useful), I'd prefer an app that lets me stream from my phone to TV a local video file, while letting me still use the phone for other things. I like movies, but get bored and would want to multitask like browse Reddit while watching said movie.

[Q]Possibility of Playing Other Media Types

So, got a question...
How hard would it be/would it be possible to cross-compile a media player for the cc (something that can be run from CLI like vlc), put it on an external storage device (if cc recognizes a connected USB device while the rom is running - maybe eureka rom, bhiga?), mount a samba share, and play a wider variety of movie formats.
So the solution would look something like this...
1. Put vlc binary on flash drive connected to cc via powered OTG cable
2. Ssh in to cc
3. Mount network samba share containing videos
4. Play whatever videos from vlc operated by cli over samba, replacing dial
Not really a programmer, and have absolutely no idea how a cc works... But it seems to me that a solution like this, while unwieldy, would allow one to bypass the limitations of cc's implementation of dial.
What do y'all think?
Sent from my SCH-I535 using XDA Premium 4 mobile app
And what about other binaries? Something like apache, php... Maybe turn the cc into a cheap webserver?
Sent from my SCH-I535 using XDA Premium 4 mobile app
I think one of the Team Eureka folks said the USB storage isn't available at normal runtime, but I could be mistaken.
Webserver is definitely possible, as that's what the Eureka Web Panel is, but general-purpose webserver use would be limited by both wireless bandwidth and moreso by the lack of storage (unless USB actually does work),
An important thing to keep in mind here... Unlike Android phones, tablets and TV sticks, Chromecast is much more scaled down and limited in design. I consider phones, tablets and TV sticks as Android-powered devices with the qualification that they are meant to be interacted with, apps installed, expanded, etc.
Think of Chromecast it more of an "accessory," black box or dumb terminal. Chromecast is more of an "extension" to those user-configurable devices.
Remember the ViewSonic AirPanel? Technically it is a computer, but a very limited (embedded) one. While it mirrored the primary screen of the computer, rather than being a second screen, it's a similar model. The AirPanel has some intelligence to accelerate the user experience but the core processing is done on the computer it's attached to.
Neither AirPanel nor Chromecast are meant to be interacted with directly at the device level, or loaded down with a lot of background processes. Chromecast doesn't have an interactive UI of its own, nor does it have external input (keyboard, mouse, touchscreen, etc) like your typical Android device does.
I wouldn't surprised if a number of "standard" libraries that your typical Android platform has simply aren't there.
I'm not saying getting VLC on it is impossible - I really don't know, but I do think it's improbable and would require a great deal of effort.
Without hardware acceleration or SDK/API support, you're relying purely on the software processing, and I haven't found much in the way of detailed specs on the platform itself. I have seen mention of the platform supporting other compression formats that Google isn't supporting yet, like MPEG-2, so it remains to be seen what Google's long-term plans are.
Not trying to be a downer here, just trying to keep things in perspective. After all, Google didn't sell us a $35 PS4 equivalent.
bhiga said:
I think one of the Team Eureka folks said the USB storage isn't available at normal runtime, but I could be mistaken.
Click to expand...
Click to collapse
So, if I'm understanding correctly, this sounds like a software limitation...Clearly the hardware is compatible - Flashcast relies on it. I don't know much about the intricacies of programming for mobile devices, but conceptually it would seem possible to make usb accessible during normal operation if it's accessible to something like Flashcast. I would love to read up on Flashcast more...it's just that normally things like flashcast which are very specific to certain hardware and require exploitation of particular holes/flaws in the software residing on that device are not normally very well documented.
How is it that Flashcast "unlocks" the functionality of USB OTG, and what limits its use when the device is booted normally? Is it something in the bootloader? Does Flashcast "hijack" the bootloader and use a different one?
EDIT: Or even how about something like this: Create an image like the recovery image that's flashed to a USB Drive, except make the "recovery image" a full ROM. That way, ROM gets access to USB device, we have much more room to put other features/binaries, etc, and then there's built in storage...Would something like that work?
tomg09 said:
How is it that Flashcast "unlocks" the functionality of USB OTG, and what limits its use when the device is booted normally? Is it something in the bootloader? Does Flashcast "hijack" the bootloader and use a different one?
EDIT: Or even how about something like this: Create an image like the recovery image that's flashed to a USB Drive, except make the "recovery image" a full ROM. That way, ROM gets access to USB device, we have much more room to put other features/binaries, etc, and then there's built in storage...Would something like that work?
Click to expand...
Click to collapse
As I understand things, FlashCast runs in recovery mode, which uses its own bootloader - which is what allows access to OTG.
If that code isn't in the normal mode bootloader, then OTG won't be accessible. It might be loadable via a kernel module, but it seems the current Android direction is to disallow loading of kernel modules (probably because it's a potential security hole).
There's more information about how and why FlashCast works in the FlashCast thread.

Wireless Phone Connection?

After Google announced almost a full year ago that Android Auto would support phone connections without needing to rely on a USB cable, I have yet to find any news on this.
Is this still happening in the aftermarket HU's? Hoping this doesn't turn into another Android Wear situation where it lacks the attention it needs to make it a market hit.
Hi,
This is called "WIFI Projection", and it's included (hidden) in the last release. No one knows how to enable AND use it. Still in alpha!
I hope current HU with wired AA support can be upgraded to wireless with a simple USB dongle (not a Wifi dongle, but with an AA wireless adapter).
Just to make sure I understood correctly: the option is there in the OS, but it doesn't work on any device as of yet? As if the software support is there, but the hardware support is not?
I'm a bit disappointed that Android Auto wasn't discussed at the I/O keynote... I think there's lots of usability updates required to improve it...
Relevant:
https://arstechnica.com/cars/2017/0...finally-ready-to-talk-about-its-car-os/?amp=1
What gets me: is it really necessary to use a a different name for this? Chromecast comes in audio-only and video forms, Pixel comes in "XL" and "C" forms also, can't they just name it something like "Android Auto Standalone" and call it a day? It serves the same end goal of getting Android into your car's radio/head unit.
Still no news of the phone-based Android Auto and wireless that I can find. That said, if everything will be integrated into the radio to begin with, I'd welcome the lack of tethering. Might even get back to developing Android apps for myself now that I have a use for them, but for my car this time! Hopefully the aftermarket guys will be smart enough to bypass Android for the sound processing though. Would hate for a resource-hogging app to kill my radio!

Categories

Resources