Just wondering as our phones have a FM receiver.
Wondering if there is a app that receives the signal and converts DAB into audio.
Should be possible i would image as a radio signal is analogue anyway..
Don't want to use streaming radio apps.
As far as i know, DAB means Digital Audio Broadcast - if your device has a digital receiver built in, that would be possible. My HD2 has only an analogue radio receiver. I do not see a way that your request could be fulfilled...
memory serves me correct there is no such thing as a digital broadcast....
All radio waves are analouge?
So if the decoder could be emulated in software?
ej2095 said:
memory serves me correct there is no such thing as a digital broadcast....
All radio waves are analouge?
So if the decoder could be emulated in software?
Click to expand...
Click to collapse
The analogue FM receiver in your phone can only receive frequencies from 87.5 to 108MHz and cannot even receive the frequencies used in DAB (174-240MHz).
If it was that easy, don't you think someone else would have already done what you suggest?
After all it would be one more advertisable feat of your Handset they would use to make you pay more money for it if they could.
lol forgot about the frequency range..
Cheers for input
Mods could you please close this thread thank you
Actually there is, it is called Wavesink and you can find it in Google store.
Unfortunately it won't work with my car player (It runs Android 2.3.4) Wavesink requiers Android 3 or newer, anyone know of a way to modify the Apk file so that it will work with earlier versions of android?
From what i have read you could modify the AndroidManifest.xml file inside the Apk but i don't have the knowledge to do that,
This programme will work with a dab Usb dongle connected to your phone, tab etc....
Dragonlove said:
Actually there is, it is called Wavesink and you can find it in Google store.
Unfortunately it won't work with my car player (It runs Android 2.3.4) Wavesink requiers Android 3 or newer, anyone know of a way to modify the Apk file so that it will work with earlier versions of android?
From what i have read you could modify the AndroidManifest.xml file inside the Apk but i don't have the knowledge to do that,
This programme will work with a dab Usb dongle connected to your phone, tab etc....
Click to expand...
Click to collapse
here in the uk there is a web site called radiofeedsuk i use this as i can download a .mp3 flile and play it va vlc once i remane it to .mp3
I think here need frequency range.. May i help you..
I would love to see a physical remote used with the chromecast. I feel that is a major item missing when it comes to controlling a set top box. This wouldn't be all that helpful with casting, but for netflix/hulu use and other apps it would be great. I like having dedicated/physical buttons for things.
Not sure where to begin on this journey. Anyone else feel the same way I do?
Possible options:
WiiMote - Bluetooth?
Keyboard - bluetooth
Is this someones attemp at a wiimote + chromecast?
https://code.google.com/p/chromecas...entation/ABI/testing/sysfs-driver-hid-wiimote
Don't know what you'd control with that.
You can use a wiimote/dualshock 3 with your android device to control YouTube, if that's what you mean.
Sent from my XT907 using xda premium
Leraeniesh said:
Don't know what you'd control with that.
You can use a wiimote/dualshock 3 with your android device to control YouTube, if that's what you mean.
Click to expand...
Click to collapse
I think they're after a physical implementation of RemoteCast
Closest thing I can think of would be to see if RemoteCast's dev would support some kind of paired Bluetooth controller like a Wiimote, but its function would still be tied to a phone/tablet somewhere.
If Chromecast does well, I wouldn't be surprised if Google releases some firmware that enables the Bluetooth part of its WiFi chip and sells us a remote and/or provides Bluetooth functionality in the SDK. But first things first, they need to release the SDK...
I would be much more interested in some IR Control myself...
Not just for when I'm using the Chromecast but for when I'm not as well.
If implemented it could automatically change your TV to the chromecast input when you cast something to Chromecast and when your not casting it would allow the Chromecast to serve as a conduit to using your tablet/phone as a full IR remote for your TV, Set Top Boxes and whatever else you have at your Home Entertainment system.
Asphyx said:
I would be much more interested in some IR Control myself...
Not just for when I'm using the Chromecast but for when I'm not as well.
If implemented it could automatically change your TV to the chromecast input when you cast something to Chromecast and when your not casting it would allow the Chromecast to serve as a conduit to using your tablet/phone as a full IR remote for your TV, Set Top Boxes and whatever else you have at your Home Entertainment system.
Click to expand...
Click to collapse
Mine already changes the channel and turns the TV on if it's off.
Unless you have an unusual setup, all you need to do is enabled HDMI-CEC in your TV's settings, and make sure Chromecast has power when the TV is off (if you want it to turn the TV on).
IR would be quite complicated, mainly because something has to receive the IR and process it.
You'd probably be better off getting a network-enabled IR receiver/blaster like the GlobalCache GC-100 to do network-triggered IR blasting.
bhiga said:
Mine already changes the channel and turns the TV on if it's off.
Unless you have an unusual setup, all you need to do is enabled HDMI-CEC in your TV's settings, and make sure Chromecast has power when the TV is off (if you want it to turn the TV on).
IR would be quite complicated, mainly because something has to receive the IR and process it.
You'd probably be better off getting a network-enabled IR receiver/blaster like the GlobalCache GC-100 to do network-triggered IR blasting.
Click to expand...
Click to collapse
I don't have that option on my TVs...
As for receiving IR.... no not what I am asking...Just for the chromecast to SEND IR and act as the globalcache device does.just on the Tx side.
I don't want to use a IR remote I want to be able to control the Home Ent system (Ir devices) via my Tablet. All I need is Tx for that and if CC had a mini plug for IR transmitter lead and some IR emitter circuitry it could do it. IR Codes would be set via the Tablet App.
Asphyx said:
I don't have that option on my TVs...
As for receiving IR.... no not what I am asking...Just for the chromecast to SEND IR and act as the globalcache device does.just on the Tx side.
I don't want to use a IR remote I want to be able to control the Home Ent system (Ir devices) via my Tablet. All I need is Tx for that and if CC had a mini plug for IR transmitter lead and some IR emitter circuitry it could do it. IR Codes would be set via the Tablet App.
Click to expand...
Click to collapse
Ahh, I see. Well, I was working within the constraints of what could potentially be done with software development and existing hardware.
Adding an IR minijack to Chromecast is well outside of that.
bhiga said:
Ahh, I see. Well, I was working within the constraints of what could potentially be done with software development and existing hardware.
Adding an IR minijack to Chromecast is well outside of that.
Click to expand...
Click to collapse
Yes but I'm already thinking towards Chromecast II! LOL
Or would they call it Chromecast 2014 like they did with the Nexus by adding rear facing camera and LTE! LOL
Asphyx said:
Yes but I'm already thinking towards Chromecast II! LOL
Or would they call it Chromecast 2014 like they did with the Nexus by adding rear facing camera and LTE! LOL
Click to expand...
Click to collapse
I'm hoping more along Chromecast 2015 - at least give the current one a full year before making it obsolete!
bhiga said:
I'm hoping more along Chromecast 2015 - at least give the current one a full year before making it obsolete!
Click to expand...
Click to collapse
Maybe we both should just hope we get rid of the whitelist before 2020! LOL
Doesnt have to be an IR remote. Could be wireless like on the Roku, or bluetooth like on the Wii.
An IR blaster on the ChromeCast would be helpful for learning remotes, so you could have 1 remote to control all of your devices.
I just prefer the physical feel of a remote. Not having to fumble around looking for capacitive buttons.
Im trying to find a cheap alternative to a Roku 3.
$35 Chromecast + remote would be cheaper than $75+ for the R3.
Why the hell do you need a physical remote when its all network based anyways? IR remote is not needed for any of the apps and an IR remote wouldn't handle all advances functions seamlessly anyways. What do you want an apple TV remote which is about worthless and constantly getting lost anyways? Perhaps and hdmi-cec network based remote might be cool but HDMI cec is still wonky though its a lot better than a few years ago.
sent from my sm-9005.
Asphyx it might be that it is not named HDMI-CEC as the diffrent vendors like to call it there own name. Here is a list over the most well known names of HDMI-CEC and it is something that have been in flat screens the last 5-6 years now so as long your tv is not older then that you should have it.
Code:
Branding Vendor
Anynet Samsung
BRAVIA Sync Sony
KURO Link Pioneer
NetCommand Mitsubishi
REGZA-LINK Toshiba
RIHD Onkyo
SimpLink LG
I am just hoping for more implementation of HDMI-CEC. I would like to use the atual tv remote to play/pause or fast fwd etc. I would also like the ability to NOT turn on the tv when i fire up google music. Now if it could turn on my receiver that would be great
ParanoidDK said:
Asphyx it might be that it is not named HDMI-CEC as the diffrent vendors like to call it there own name. Here is a list over the most well known names of HDMI-CEC and it is something that have been in flat screens the last 5-6 years now so as long your tv is not older then that you should have it.
Code:
Branding Vendor
Anynet Samsung
BRAVIA Sync Sony
KURO Link Pioneer
NetCommand Mitsubishi
REGZA-LINK Toshiba
RIHD Onkyo
SimpLink LG
Click to expand...
Click to collapse
Yes but I'm almost certain that standard was made more recently than the TV I have...
I pretty much have a first Gen HDTV and believe the CEC Protocal was not part of HDMI 1.1
It wasn't available until HDMI 1.2a if I'm not mistaken.
I could check for a firmware upgrade but merely changing the channel on the TV to Chromecast is only part of what I would like it to do.
I suppose I will have to spring for the $200 IRoverIP blaster to get it.
scoobdude said:
I am just hoping for more implementation of HDMI-CEC. I would like to use the atual tv remote to play/pause or fast fwd etc.
Click to expand...
Click to collapse
Many would find that handy - so it is a bit strange that it has not yet been implemented. One reason might be that the chromecast team want to emphasise that a remote is not necessary and that controlling using a mobile device is preferable. I guess that it will be added down the road (just like the delete button was added to gmail).
Arne S said:
Many would find that handy - so it is a bit strange that it has not yet been implemented. One reason might be that the chromecast team want to emphasise that a remote is not necessary and that controlling using a mobile device is preferable. I guess that it will be added down the road (just like the delete button was added to gmail).
Click to expand...
Click to collapse
Actually the most likely reason is they wanted to keep the cost down at it's current $35 and adding any IR or extra CEC support would have driven the price up another 10-20 dollars.
These things we are hoping for may all show up whenever Chromecast II comes along.
Right now they are competing with Miracast dongles that can be had for around the same price point.
I think the target with this initial version was to do Miracast better because it can work over wired networks as well and frees the device that initializes the stream to do other things..
Not possible with Miracast!
Asphyx said:
Actually the most likely reason is they wanted to keep the cost down at it's current $35 and adding any IR or extra CEC support would have driven the price up another 10-20 dollars.
Click to expand...
Click to collapse
The chromecast is already using some CEC functions so additional HW would be probably not be required to implement support for using the TV remote to control the dongle.
Arne S said:
The chromecast is already using some CEC functions so additional HW would be probably not be required to implement support for using the TV remote to control the dongle.
Click to expand...
Click to collapse
Big difference between adding a Transistor or two to a chip that will make a contact to switch to the current input or Power On than it is to put an entire set of them that can do much more complex functions. Just the TV compatibility alone would add to the price.
I agree it should be possible to do easily but these things all need to be added to the silicon which would make it cost more.
This is SOP for any new device you're trying to get adopted. The Next gen will probably add a ton of things to inspire upgrading to it.
Remember the Nexus7 (2012) came with no Rear Facing Camera or LTE to keep the price down as well....
Fast Forward to 2013 and Nexus 7 (2013) has BOTH included!
This version we have now is a proof of concept device, Gets us hooked and serves as a starter platform to get 3rd Party support for it's innovative streaming methods.
And now that is done so the 3rd parties can start making it useful while Google thinks up what the next generation can do that the first gen doesn't do but probably should!
Just a matter of time of you ask me...And don't be surprised to see some Chromecast functionality built into your smart TV that has the full blown IR and CEC support your looking for.
Here is a list of all the functions CEC does most of which have no useful application regarding Chromecast until such time as they decide using Chromecast as an IP Remote device is something they really want to do. And most are not applicable other than play stop and pause.
One Touch Play allows devices to switch the TV to use it as the active source when playback starts (Currently Supported I believe)
System Standby enables users to switch multiple devices to standby mode with the press of one button
Preset Transfer transfers the tuner channel setup to another TV set
One Touch Record allows users to record whatever is currently being shown on the HDTV screen on a selected recording device
Timer Programming allows users to use the electronic program guides (EPGs) that are built into many HDTVs and set-top-boxes to program the timer in recording devices like PVRs and DVRs
System Information checks all components for bus addresses and configuration
Deck Control allows a component to interrogate and control the operation (play, pause, rewind etc.), of a playback component (Blu-ray or HD DVD player or a Camcorder, etc.) (This is what your looking for I sure wouldn't mind having this)
Tuner Control allows a component to control the tuner of another component
OSD Display uses the OSD of the TV set to display text
Device Menu Control allows a component to control the menu system of another component by passing through the user interface (UI) commands
Routing Control controls the switching of signal sources (Currently Supported)
Remote Control Pass Through allows remote control commands to be passed through to other devices within the system (I want THIS!)
Device OSD Name Transfer transfers the preferred device names to the TV set
System Audio Control allows the volume of an AV receiver, integrated amplifier or pre-amplifier to be controlled using any remote control from a suitably equipped device(s) in the system (You and I would BOTH like this!)
Asphyx said:
Big difference between adding a Transistor or two to a chip that will make a contact to switch to the current input or Power On than it is to put an entire set of them that can do much more complex functions. Just the TV compatibility alone would add to the price.
I agree it should be possible to do easily but these things all need to be added to the silicon which would make it cost more.
Click to expand...
Click to collapse
That might be. I do not know. The Chromcast is powered by the Marvel Armanda 1500-mini chip which is also used in other devices. I do not know what CEC capabilities this chip has but according to its documentation it supports HDMI v1.4 while CEC was introduced in v1.3. I think that both the fact that this is a "standard" chip also used in other devices and the fact that it uses HDMI v1.4 points in the direction that the HW in the Chromecast dongle supports more CEC functions than the ones currently exposed.
Hi everyone, first time poster so I'm sorry if this isn't the right forum to post in, but I felt like it was the closest I could think of.
I'm trying to find a way to mimic how the chromecast causes a tv to switch to the input of the chromecast dongle. I have an Android Box that came rooted and has HDMI-CEC capability. What I'm looking to do is somehow use Tasker to trigger the CEC-switch activity/intent/whatever to have my tv (turn on) and switch to the HDMI source of the Android Box (the box will be left on 24/7 and tasker will continually run as background service on the box). Basically, I'm trying to imitate the chromecast's cast action to bring me to my Android Box's input and ultimately it's home screen.
That's where I'm stuck at the moment. Things I've thought might work:
1. Wake-On-Lan (Doesn't seem to wake the box, even when I've checked to make sure the power button made the box sleep and not perform a full shutdown) Tried-Unsuccessful
2. AutoCast to have the box cast to itself, but it doesn't have chromecast/miracast/etc built-in as far as I can tell according to the specs and see anything about cast ability while browsing through its menus.
3. Using Android's HDMI-CEC library in a Java Action in Tasker to imitate the CEC switch sources intent/activity. However, I just recently learned that Google decided to lockdown their API for HDMI-CEC interactivity, so that scrubs that idea.
4. The best bet, and what gave me the idea to post here, is this App Cast Receiver that was created by another user on these forums that seems to accomplish something close to what I'm trying to do in allowing an android device to imitate a chromecast device. If I were able to use this couldn't I then use the AutoCast app I mentioned above to have the Android Box cast to itself, then stop the AutoCast app a few seconds later (after giving the box's CEC capability enough time to make the tv switch sources)? But, unfortunately it appears the app has since been deserted and won't work with the newer chromecast sdk. Maybe someone has an alternative app?
Since this is my first Android Box I'm not quite sure how Tasker actions function when ran from the box. Example: Would a Wake Screen Action trigger a switch of HDMI inputs?
So, after exhausting all my ideas after coming up with nothing in my searches I figured I'd ask the community here since this seems to be a pretty dev/mod-heavy community (and I love it). I'm not sure if this would be better suited for the Tasker or AMLogic Android Box forums on here. If so, I'll happily move the post if a mod cannot do so for me.
TL;DR: Looking for some way, be it app or otherwise, to imitate chromecast behavior (utilizing CEC) in order to make tv switch source to a running Android Box's homescreen.
Hey! tell me more about 3, I was looking to have a Raspberry Pi act as a go-between to simulate CEC with a non-CEC TV by receiving my remotes IR codes and sending either CEC codes to the ChromeCast or using the CC API to pause/stop play - but only reverse engineered versions are available on Pi.
The Pi has built-in CEC support so you can use `apt-get install cec-tools` and then play with the `cec-client` to do some interesting stuff. The ChromeCast in my case has an invalid address so I don't seem to be able to activate pause play. (I see a logical address of 4 but also an address of `f.f.f.f`, ie invalid).
Anyways, it may be worth playing with a Pi and seeing if HDMI-CEC will do what you want, and then seeing if you can get a CEC library for android and just recreate the Pi work. Less hoops to jump around.
I don't know enough about the Android side. The CC API has an Android implementation so I would think you'd be able to do everything you want, iff it does the switching. I've done very little development on Android (a meteor app and an Android native camera library work), unfortunately. (If the Pine64 supports CEC I may end up going down this route).
I've posted more about my interest here: on reddit /r/Chromecast/comments/5znpuk/i_want_to_use_a_raspberry_pi_to_control_the/
jlongman said:
Hey! tell me more about 3, I was looking to have a Raspberry Pi act as a go-between to simulate CEC with a non-CEC TV by receiving my remotes IR codes and sending either CEC codes to the ChromeCast or using the CC API to pause/stop play - but only reverse engineered versions are available on Pi.
The Pi has built-in CEC support so you can use `apt-get install cec-tools` and then play with the `cec-client` to do some interesting stuff. The ChromeCast in my case has an invalid address so I don't seem to be able to activate pause play. (I see a logical address of 4 but also an address of `f.f.f.f`, ie invalid).
Anyways, it may be worth playing with a Pi and seeing if HDMI-CEC will do what you want, and then seeing if you can get a CEC library for android and just recreate the Pi work. Less hoops to jump around.
I don't know enough about the Android side. The CC API has an Android implementation so I would think you'd be able to do everything you want, iff it does the switching. I've done very little development on Android (a meteor app and an Android native camera library work), unfortunately. (If the Pine64 supports CEC I may end up going down this route).
I've posted more about my interest here: on reddit /r/Chromecast/comments/5znpuk/i_want_to_use_a_raspberry_pi_to_control_the/
Click to expand...
Click to collapse
Here's the link to Android's documentation for the HDMI-CEC Control Service. But, like I said it's been locked down and only allows system-level access now.
I don't have any Pi at my disposal (plus my Android Box also has built-in CEC-capability/functionality) and since my situation doesn't actually involve chromecast I never thought to look at their api/sdk. But, I was able to finally solve my problem with a painfully simple, yet not that intuitive or logical method. The way my box's os/firmware appears to work is by firing the cec signal to switch inputs only on its boot_complete and wake_from_standby procedures. My solution just simulates pressing the Standby button twice in a row via Shell command (with Root option checked) from within Tasker. Logically, I thought after the first press the box wouldn't respond to the second press due to already being in standby mode (because of the first button press). But, it turns out both simulated presses occur (maybe keyevents are queue?), allowing me to put the box in standby momentarily and immediately bring it out of standby, which triggers the wake_from_standby procedure and in turn causes the input to switch (or my tv to turn on then input to switch).
My thought with the Pi and CC API was that you would use the PI to monitor the HDMI-CEC bus as the output is controlled by the CC - assuming it switches the input to itself but my TV doesn't support HDMI so maybe that's a bad assumption - and then use that knowledge to replay using the Android HDMI-CEC API. And not understanding what you meant by the API being locked down. That kind of sucks - I was hoping Android would be another bridge platform if the Pi failed me.
Well congrats on a working solution. Cheers!
Hi,
I'm currently building a Raspberry Pi (3) Android Auto project for my 55 year old Land Rover. I'm using Openauto installed on Raspbian (rather than using Crankshaft) so I can also add reversing cameras, ultrasonic sensors and so on, more easily.
Anyway, I the system so far:
RPi 3b running Raspbian Stretch
7" Touchscreen
USB soundcard with mic input.
It took a while but I finally configured the audio and it's working, at least Google Assistant and I think Navigation prompts (but it's difficult to assess that, the system isn't installed yet so it isn't going anywhere). The problem I am having is I can't get music at all. The music apps work, and I can use BBC iPlayer Radio no problem. I just can't get either Google Play Music or Pulsar working with locally stored files - There isn't any sound output at all. Mike input works, I tested the soundcard in Raspbian and it outputs audio now (after finding a guide and editing configs, it didn't work at first out of the box)
I'm not an expert on Linux or Android, I'm following guides so consider me a beginner if you would please! Also, if this has been covered before, I do apologise for bringing it up again, any and all help is very much appreciated. I also apologise if it is forum etiquette to introduce oneself before asking questions, I don't mean to be rude.
And here I was thinking the most difficult step would be figuring out how to mount/fit everything into the old bus...
Many thanks,
Ste
Good morning everyone,
I am interested in buying one radio model DASAITA PX6 with DSP. I have a mazda cx5 from 2014.
But as I see in the ad it is compatible with the steering wheel controls but not with the control jostick.
I don't know if you know if there is an application to manually configure the functions of those buttons with the DASAITA options. I found some video that talks about a "REDMOD" fireware with parameterization options but I don't know if this is compatible with the DASAITA radio.
For me, using the joystick is vital. Can you help me?
No yes if I have put this message in the corresponding category.
Thank you very much and greetings.