Related
We have a MiraCast capable dongle that I'd like to try connecting to with my Nook. I'm runing CM 10.1.3 right now, which I think is a new enough version of Android, and I don't see any Miracast options in the Display settings. Is it just not in the CM builds for Nook HD+?
Thank you!
Bump. Any news on Miracast support? I'm also interested.
Sent from my BN Nook HD using Tapatalk
Yeah I would also love this feature added.
So I upgraded to CM11 last night. I noticed that Miracast support appears to be present in it. I tried it, but it doesn't see either of the Miracast capable devices near me (one Netgear and one Actiontec). My Nexus 5 sees both.
Assuming the support isn't disabled in some other way, I'm guessing that the hardware in the Nook HD+ may not be sufficient. I wouldn't be surprised if there was a dual radio requirement for miracast to work. You wouldn't be able to have network access and cast at the same time if you didn't have dual radios for instance.
Thanks! I also installed cm11 and noticed the option. Tried to connect to my Sony TV, but it doesn't appear be able to see the TV. I hope it is not a hw limitation...
Sent from my BN Nook HD using Tapatalk
colema19 said:
So I upgraded to CM11 last night. I noticed that Miracast support appears to be present in it. I tried it, but it doesn't see either of the Miracast capable devices near me (one Netgear and one Actiontec). My Nexus 5 sees both.
Assuming the support isn't disabled in some other way, I'm guessing that the hardware in the Nook HD+ may not be sufficient. I wouldn't be surprised if there was a dual radio requirement for miracast to work. You wouldn't be able to have network access and cast at the same time if you didn't have dual radios for instance.
Click to expand...
Click to collapse
I am running CM11 on my Nook HD and have been able to successfully use Miracast only from the YouTube app. No other connection attempt seems to work, but YouTube definitely does. Quality is not particularly good, though.
danshane said:
I am running CM11 on my Nook HD and have been able to successfully use Miracast only from the YouTube app. No other connection attempt seems to work, but YouTube definitely does. Quality is not particularly good, though.
Click to expand...
Click to collapse
Are you talking about Chromecast? It doesn't sound like you are talking about Miracast. They aren't the same thing, if you are.
colema19 said:
Are you talking about Chromecast? It doesn't sound like you are talking about Miracast. They aren't the same thing, if you are.
Click to expand...
Click to collapse
I do not have Chromecast. It is definitely Miracast that I am referring to. Miracast is a feature on my Panasonic Blu-ray player, and the Android YouTube app specifically requests to connect to Miracast, not Chromecast.
danshane said:
I do not have Chromecast. It is definitely Miracast that I am referring to. Miracast is a feature on my Panasonic Blu-ray player, and the Android YouTube app specifically requests to connect to Miracast, not Chromecast.
Click to expand...
Click to collapse
Ah cool, I didn't realize that there were devices with Miracast support. So, I'm not surprised that Youtube looks bad. Were you watching a HD video, and in HD? If not, it was upscaled, which would mean it looks awful.
colema19 said:
Ah cool, I didn't realize that there were devices with Miracast support. So, I'm not surprised that Youtube looks bad. Were you watching a HD video, and in HD? If not, it was upscaled, which would mean it looks awful.
Click to expand...
Click to collapse
I was watching an HD (720p) video on YouTube. It looked more like SD on my 73" DLP TV. I streamed the same video through the YouTube app on my Panasonic BD player and the resolution was great.
So in my opinion, based only on my experience, Miracast does not work any better than Chromecast when it comes to redirecting video from a tablet or phone (though the concept is undoubtedly cool). Direct connection still wins out.
build.prop hack to enabling Miracast option.
Code:
$ adb root
$ adb remount
$ adb pull /system/build.prop
(add persist.debug.wfd.enable=1 to build.prop)
$ adb push build.prop /system/
$ adb shell chmod 644 /system/build.prop
$ adb reboot
after editting build.prop, settings -> display -> Cast screen -> Wireless Display check option appears.
but this is only option showing hack. I don't know your device Miracast compatibility.
s107ken, how to use this code? paste it in build.prop?
RumBle said:
s107ken, how to use this code? paste it in build.prop?
Click to expand...
Click to collapse
It probably won't matter. I didn't realize at the time I asked, that the Nook HD+ doesn't have the hardware to support miracast (dual wifi radios).
I try to use this code, not work.
Sent from my HTC One X+ using XDA Free mobile app
A year later, still can't Cast Screen using Miracast to my Roku3 (as a Miracast receiver)...
shdware said:
A year later, still can't Cast Screen using Miracast to my Roku3 (as a Miracast receiver)...
Click to expand...
Click to collapse
It will never work. The Nook HD+ does not have the required hardware to support Miracast.
colema19 said:
It will never work. The Nook HD+ does not have the required hardware to support Miracast.
Click to expand...
Click to collapse
I'm not entirely sure of that.
Kensuke has apparently been successful with miracast on OMAP.
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki
Also TI has a page on wi-fi direct,
http://processors.wiki.ti.com/index...tivity_NLCP_WiFi_Direct_Configuration_Scripts
Unfortunately his patches are for AOSP. Although it appears he also developed some patches for CM11.
http://forum.xda-developers.com/showpost.php?p=49265142&postcount=118
If someone could convince him to release his CM11 patches source....
until then it would be worth a try to install his miracast update on CM11. (The libraries should be very similar to ours anyway.)
http://forum.xda-developers.com/attachment.php?attachmentid=2505154&d=1389302451
colema19 said:
It probably won't matter. I didn't realize at the time I asked, that the Nook HD+ doesn't have the hardware to support miracast (dual wifi radios).
Click to expand...
Click to collapse
miracast doesn't required dual wifi, require wifi direct support.
Nexus 7 2012 has 2.4Ghz wifi only but miracast is working.
first, nook supported wifi direct?
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/How-to-use-Miracast?#wi-fi-wi-fi-direct
if failed changes device name, it's meaning don't support wifi direct, the another problem for miracast.
Sent from my GT-I9305 using XDA Free mobile app
s107ken said:
miracast doesn't required dual wifi, require wifi direct support.
Nexus 7 2012 has 2.4Ghz wifi only but miracast is working.
first, nook supported wifi direct?
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/How-to-use-Miracast?#wi-fi-wi-fi-direct
if failed changes device name, it's meaning don't support wifi direct, the another problem for miracast.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think it needs dual band. I think it needs dual radios. Wifi direct is a requirement yes, but I think dual radios is also a requirement because otherwise it cannot maintain a network connection at the same time. Strictly speaking it shouldn't need a network connection as well, but I haven't seen anything that has Miracast that doesn't have dual radios I have 3 miracast capable devices, and all have dual radios. I have gone through several devices that have miracast options, but drop immdiately after a connect attempt because the device attempts to re-grab the wifi device to use as a network connection, which interrupts the Miracast Wifi direct connection. That's why you need 2 radios, one for the Wifi direct, one for Android to use as an active network connection. Or at least to grab onto and not interfere with the Miracast connection. I'd be happy to be incorrect here, but my experience suggests that is the issue.
Sorry, correction here, it isn't dual radios that I think are needed, but dual antennas (I got the hardware piece wrong in my head). It is interesting though, that page says that he's got it working on a 2012 Nexus 7 which I believe is only a single antenna. So maybe I am way wrong here.
But, that said, I still stand by what my experience has been thus far...everything that does work has dual antennas, and everything that doesn't, doesn't have dual antennas. It could very well be in the case that you don't have dual antennas, the radio hardware itself becomes much more critical, so maybe why it may work in that Nexus 7 but hasn't worked in my devices.
I was messing around with the wireless display feature of my tablet and I realized that I could mirror to my tv because I have an android box connected to it that is also running 4.2. My question is does it matter what OS my android box is running at? The fact that it's also 4.2, is that a coincidence or a necessity?
Also, it sucks. Very slow, super duper lag. Do you think a dedicated Miracast dongle would improve the performance?
siratfus said:
I was messing around with the wireless display feature of my tablet and I realized that I could mirror to my tv because I have an android box connected to it that is also running 4.2. My question is does it matter what OS my android box is running at? The fact that it's also 4.2, is that a coincidence or a necessity?
Also, it sucks. Very slow, super duper lag. Do you think a dedicated Miracast dongle would improve the performance?
Click to expand...
Click to collapse
As I understand it Miracast isn't supported earlier than Android 4.2 aka JellyBean+
I wasn't aware you could go device-to-device. If so, that's pretty cool!
I'd investigate but the only Miracast-capable device I have is my phone (running 4.3) - other devices I have access to are all 4.1 or earlier.
bhiga said:
As I understand it Miracast isn't supported earlier than Android 4.2 aka JellyBean+
I wasn't aware you could go device-to-device. If so, that's pretty cool!
I'd investigate but the only Miracast-capable device I have is my phone (running 4.3) - other devices I have access to are all 4.1 or earlier.
Click to expand...
Click to collapse
So when you turn on the wireless display of your 4.3 phone, it doesn't pick up your 4.1 phones?
Now that I think about it, I have other smartphones in the house too. It doesn't seem them. So yeah, I guess both transmitter and receiver has to be 4.2 and up.
Yeah same situation here. The 4.1 Samsung has AllShare but the 4.1 Toshiba tablet got nothin.
Either way, neither have Miracast.
-= this post enhanced with bonus mobile typos =-
siratfus said:
I was messing around with the wireless display feature of my tablet and I realized that I could mirror to my tv because I have an android box connected to it that is also running 4.2. My question is does it matter what OS my android box is running at? The fact that it's also 4.2, is that a coincidence or a necessity?
Also, it sucks. Very slow, super duper lag. Do you think a dedicated Miracast dongle would improve the performance?
Click to expand...
Click to collapse
Are you sure you are using the Android box to do the mirroring? I'm almost positive this functionality is not available yet (mirror to another Android device). Are you sure you TV does not have Miracast built in?
rkirmeier said:
Are you sure you are using the Android box to do the mirroring? I'm almost positive this functionality is not available yet (mirror to another Android device). Are you sure you TV does not have Miracast built in?
Click to expand...
Click to collapse
Positive. The tv is not "smart." Plus what else can it be since I'm playing with the Android Box? What I mean is my Android Box uses HDMI input 2. If the TV is doing the mirror display, wouldn't I need to change the input source and get out of HDMI input 2? The Android Box has an app that I have to go through, and it would say "Waiting for the Renderer..." On my tablet, under wireless display, I see the Android Box, I hit connect. The Android Box then says something to the effect.. "Receiving display request..."
Then it mirrors, but it completely sucks. Sometimes it won't even mirror and the TV would just keep saying "Receiving display request.." forever.
siratfus said:
Positive. The tv is not "smart." Plus what else can it be since I'm playing with the Android Box? What I mean is my Android Box uses HDMI input 2. If the TV is doing the mirror display, wouldn't I need to change the input source and get out of HDMI input 2? The Android Box has an app that I have to go through, and it would say "Waiting for the Renderer..." On my tablet, under wireless display, I see the Android Box, I hit connect. The Android Box then says something to the effect.. "Receiving display request..."
Then it mirrors, but it completely sucks. Sometimes it won't even mirror and the TV would just keep saying "Receiving display request.." forever.
Click to expand...
Click to collapse
What is the app?
Hello everyone. Week ago I've became a happy user of Xperia Z1, and one of first things, that I've tested is a screen mirroring, as i have a TV which supports miracast and has an option to Enable\Disable DRM support. It worked flawlessly. Yes, there was a lag up to 500ms, but for me that's OK. Then i've updated firmware to 4.4.2 and lost ability to stream phone's screen on TV. Changed many firmwares, including customs, but no luck. Connection dialog opens both on TV and Z1, but terminates automatically with message, that TV does not support HDCP. I can stream audio\video\photo via WiFi, but not phone's screen. As i understand, HDCP is a protection, wich allows to run DRM-encrypted media. And my TV should be able (and surely was able) to stream it. Just tested same feature on Xperia C with my TV, it works. Have anyone seen such problem, or knows a way to disable HDCP on Z1?
I imagine you have unlocked your bootloader?
I am not 100% sure but you said the connection depends on DRM keys; you lose these when you unlock the bootloader.
gregbradley said:
I imagine you have unlocked your bootloader?
I am not 100% sure but you said the connection depends on DRM keys; you lose these when you unlock the bootloader.
Click to expand...
Click to collapse
Nice one, but miss. My bootloader never changed, as i used only firmwares, not kernels. And first mirroring didn't asked for keys or something, only permitting dialog on TV screen.
gregbradley said:
I imagine you have unlocked your bootloader?
I am not 100% sure but you said the connection depends on DRM keys; you lose these when you unlock the bootloader.
Click to expand...
Click to collapse
Your are not sure about that but this make me think, are we able to connect with UB anyway?
Well I am at a loss.
I just a MHL to HDMI cable to mirror the screen on the TV and it works fine.
Sorry I cant help more
gregbradley said:
Well I am at a loss.
I just a MHL to HDMI cable to mirror the screen on the TV and it works fine.
Sorry I cant help more
Click to expand...
Click to collapse
MHL fork for me too, but it's really more comfortable when there's only phone in your hands and picture is on big screen.
Blue2s said:
MHL fork for me too, but it's really more comfortable when there's only phone in your hands and picture is on big screen.
Click to expand...
Click to collapse
True. I will be glad if someone know how to fix it so I will know more about it and maybe I will test ti too to understand if that working on UB.
Blue2s said:
Hello everyone. Week ago I've became a happy user of Xperia Z1, and one of first things, that I've tested is a screen mirroring, as i have a TV which supports miracast and has an option to Enable\Disable DRM support. It worked flawlessly. Yes, there was a lag up to 500ms, but for me that's OK. Then i've updated firmware to 4.4.2 and lost ability to stream phone's screen on TV. Changed many firmwares, including customs, but no luck. Connection dialog opens both on TV and Z1, but terminates automatically with message, that TV does not support HDCP. I can stream audio\video\photo via WiFi, but not phone's screen. As i understand, HDCP is a protection, wich allows to run DRM-encrypted media. And my TV should be able (and surely was able) to stream it. Just tested same feature on Xperia C with my TV, it works. Have anyone seen such problem, or knows a way to disable HDCP on Z1?
Click to expand...
Click to collapse
I had the same issue before, on my SAMSUNG SMART TV with my XPERIA Z1, the solution, I just updated the TV's firmware and there you go, screen mirroring worked!
I'm on STOCK KK .757 by the way.
Blue2s said:
Hello everyone. Week ago I've became a happy user of Xperia Z1, and one of first things, that I've tested is a screen mirroring, as i have a TV which supports miracast and has an option to Enable\Disable DRM support. It worked flawlessly. Yes, there was a lag up to 500ms, but for me that's OK. Then i've updated firmware to 4.4.2 and lost ability to stream phone's screen on TV. Changed many firmwares, including customs, but no luck. Connection dialog opens both on TV and Z1, but terminates automatically with message, that TV does not support HDCP. I can stream audio\video\photo via WiFi, but not phone's screen. As i understand, HDCP is a protection, wich allows to run DRM-encrypted media. And my TV should be able (and surely was able) to stream it. Just tested same feature on Xperia C with my TV, it works. Have anyone seen such problem, or knows a way to disable HDCP on Z1?
Click to expand...
Click to collapse
http://userguide.sonymobile.com/referrer.php?region=gb&product=xperia-z1#Screen-mirroring.html
Prefer the DLNA and the Throw system or use a MHL to HDMI cable
The HDCP is just painfull and broken.
kram.flores said:
I had the same issue before, on my SAMSUNG SMART TV with my XPERIA Z1, the solution, I just updated the TV's firmware and there you go, screen mirroring worked!
I'm on STOCK KK .757 by the way.
Click to expand...
Click to collapse
Yes, tried that too. My Phillips TV found and installed update, Samsung TV found nothing. But nothing changed, Phillips shows in connections menu, Samsung not (i think Samsung TV simply does not supports miracast)
Just found pack of patches for other android phones, which fixes screen mirroring. It's said, that screen mirroring stops working after rooting, and patch disables HDCP completely. There's a patch for Snapdragon 800, which i just applied, and got a confirmation, that it's working, but with opposite effect- screen mirroring service stops with error. So all we need now is to change patch (file /system/vendor/lib/libwfdsm.so) for xperia (and maybe some others) devices. Or it's pretty possible that screen mirroring will work if we just replace current libwfdsm.so with an older version, which surely works. I'm ready to run experiments on my Z1, just need that file from older firmware.
any update from this issue? I got the same probably after 4.4.4 update.
I have a Z1 and am having the same HDCP issue with a brand new Microsoft Miracast dongle.
According to the Sony support forum, Sony has updated to the "Latest" version of the HDCP standard and all these other devices are on an old version.
Sony is paranoid that we are all going to steel their content. Apparently they don't realize that this lack of compatibility only hurts hones customers,
the thieves already know how to get around these systems.
If anyone has older software I would love to try the option above.
I hate having to open the USB port every time I get into my car, I just want to cast the screen to my AppRadio. Sony should have made the magnetic charge port also support magnetic MHL out.
Apparently 5.0 will solve this but for now we are all stuck on 4.4.4 or older.
CharlesG70 said:
I have a Z1 and am having the same HDCP issue with a brand new Microsoft Miracast dongle.
According to the Sony support forum, Sony has updated to the "Latest" version of the HDCP standard and all these other devices are on an old version.
Sony is paranoid that we are all going to steel their content. Apparently they don't realize that this lack of compatibility only hurts hones customers,
the thieves already know how to get around these systems.
If anyone has older software I would love to try the option above.
I hate having to open the USB port every time I get into my car, I just want to cast the screen to my AppRadio. Sony should have made the magnetic charge port also support magnetic MHL out.
Apparently 5.0 will solve this but for now we are all stuck on 4.4.4 or older.
Click to expand...
Click to collapse
No updates to this? Im trying to get this working with xbox one, but that same error screen popping up...stock lollipop z1 compact
Sent from my D5503 using Tapatalk
Hey guys, I asked this question on AndroidCentral and no replies since 2 weeks, so I'm asking here
I have a 2016 Golf which has Android Auto.
I also have an old Galaxy Note 2 (SGH-1317M) which runs very fine but wasn't compatible with Android Auto.
Yesterday, I rooted the device and flashed a new rom to 5.1.1
For now, Google lets me download the Android Auto app on the phone. However, when I connect it to my car, it says that my device is not compatible. I am also able to open the app on my phone but it says that my phone is not compatible either.
Is there a way to change the "name" of my device to make it compatible at that point (I heard a build.prop file but i'm not sure).
For now, the device model in my settings is "GT-N7105". Let's say I would change the name for the Galaxy Note 5 name.
Before modifying the Build.prop, I just want to make sure that it will work.
Thanks!
Hi all,
I'm looking as well for such kind of information - I have a Galaxy S3 but saw tha same as in the box from MAAYO...
So, anyone has a solution to this?
Best Regards
Magic01
Look in to changing the name on the build prop, but i dont think its going to help. For the most part i think the hardware set is whats preventing it from working. Some phones dont have MHL to connect to the head unit, and some only work with the international version of the phone.
My wife's phone (doogee f5) doesn't have MHL but it works with android auto, so I don't think that's the problem.
OTOH mine (homtom ht7 pro) doesn't work.
Both phones run android 5.1 and have the same set of codecs, if is there a way to make mine work by tweaking the build.prop I'd really like to know.
Edit I just checked and my son's phone (moto e 2nd gen.) also works, so it's not the memory either (1 GB on the moto e vs. 2 on mine). It seems the only phone that's not working is mine
Google dropped MHL in favor of Cast. None of their software will require MHL.
Note that Nexus 6 completely lacks MHL, yet is fully compatible with AA.
Yes, as you say (and as I have tested) the lack of MHL cannot be the cause of the incompatibility.
The help(less) center tells that the cause could be a missing codec or not enough ram, but it cannot be neither the codecs (both phones have the same set of codecs available) nor the ram (I checked with a moto e with just 1GB ram and it has no problem connecting to the in dash display).
Google should tell the exact cause of the incompatibility, so we could at least know if a tweak of build.prop could fix the issue
Oh, wait, maybe that's the reason they don't....
I've been searching the forum without much success, I want to install the Chromecast OS ( or in this case, HubCap) on a general cheap android tablet. Since Chromecast is similar in foundation, is this possible? I would like the tablet I get, like an 8" Chinese generic or anything, which already has wifi and a display, to be the display I can choose to cast to.
My further thoughts is that it makes a portable video frame I can use with my Google Home, but that's for my own further experimentation. I still haven't been able to find if HubCap on Chromecast still allows the Chromecast to be controllable from Google Home, though I would assume so.
Any directions I should look into? I would love it to be as easy as rooting the tablet device and installing a HubCap slip-streamed Chromecast package ( if any were to exist, even ) , but I have a feeling it's not that easy, despite Android seeming to be resilient as to the platform it is being installed on.
Ty
werelwolf said:
I've been searching the forum without much success, I want to install the Chromecast OS ( or in this case, HubCap) on a general cheap android tablet. Since Chromecast is similar in foundation, is this possible? I would like the tablet I get, like an 8" Chinese generic or anything, which already has wifi and a display, to be the display I can choose to cast to.
My further thoughts is that it makes a portable video frame I can use with my Google Home, but that's for my own further experimentation. I still haven't been able to find if HubCap on Chromecast still allows the Chromecast to be controllable from Google Home, though I would assume so.
Any directions I should look into? I would love it to be as easy as rooting the tablet device and installing a HubCap slip-streamed Chromecast package ( if any were to exist, even ) , but I have a feeling it's not that easy, despite Android seeming to be resilient as to the platform it is being installed on.
Ty
Click to expand...
Click to collapse
This is extremely doubtful...
Sent from my SM-G935V using Tapatalk
turn rooted galaxy S6 into chromecast and/or Fire Tv box...help? (please)
werelwolf said:
I've been searching the forum without much success, I want to install the Chromecast OS ( or in this case, HubCap) on a general cheap android tablet. Since Chromecast is similar in foundation, is this possible? I would like the tablet I get, like an 8" Chinese generic or anything, which already has wifi and a display, to be the display I can choose to cast to.
My further thoughts is that it makes a portable video frame I can use with my Google Home, but that's for my own further experimentation. I still haven't been able to find if HubCap on Chromecast still allows the Chromecast to be controllable from Google Home, though I would assume so.
Any directions I should look into? I would love it to be as easy as rooting the tablet device and installing a HubCap slip-streamed Chromecast package ( if any were to exist, even ) , but I have a feeling it's not that easy, despite Android seeming to be resilient as to the platform it is being installed on.
Ty
Click to expand...
Click to collapse
I believe I am looking for the same thing! I just recently upgraded to the galaxy s8. My old device is a rooted galaxy s6. I would like to use the galaxy s6 to hook up to my LG HDTV (model is LG 55LF6000, a "dumb" tv and is not wifi capable). I have been searching for "a way to turn the gs6 into a chromecast and/or Fire Tv". The hope is that I can then turn my "dumb" TV into a SmartTV and (hopefully) be able to utilize KODI as well as other smarttv type functions as if it were one to begin with.
As a side note, I have had every single samsung "galaxy s" phone; even before they were noted as such, starting with the samsung moment, the epic 4g touch, all the way up. I have rooted every single one of them, BUT I DO NOT want to root my Galaxy S8 (sungstratum mods do wonders without a need for root) bc Im in love with some of the knox features (secure folder, samsung pass etc) never having used any before due to using rooted devices.
I did find a few forums that appeared to mention ways to sort of do this, where the receiving device needed to be rooted (in my case the gs6) and the sending one did not need to be rooted (gs8). However, I cannot find them anymore, they were rather old (2015 I believe) and weren't descriptive enough or easy to follow in order to get the job done... So round-about-way of saying/asking... I think we are looking for the same thing, correct?
Wish/Help Request (summarized): use old android device as chromecast/fire Tv (rooted gs6) connected to "dumb", no wifi, HDTV // using newer android device (gs8) as the remote/casting device (chromecast) or as the Fire Tv remote if going that route is possible also... SOMEBODY, PLEASE HELP US! <Many thanks in Advance!
-E.Almighty777 (I've got that god-complex ;-P )
EvanAlmighty777 said:
I believe I am looking for the same thing! I just recently upgraded to the galaxy s8. My old device is a rooted galaxy s6. I would like to use the galaxy s6 to hook up to my LG HDTV (model is LG 55LF6000, a "dumb" tv and is not wifi capable). I have been searching for "a way to turn the gs6 into a chromecast and/or Fire Tv". The hope is that I can then turn my "dumb" TV into a SmartTV and (hopefully) be able to utilize KODI as well as other smarttv type functions as if it were one to begin with.
As a side note, I have had every single samsung "galaxy s" phone; even before they were noted as such, starting with the samsung moment, the epic 4g touch, all the way up. I have rooted every single one of them, BUT I DO NOT want to root my Galaxy S8 (sungstratum mods do wonders without a need for root) bc Im in love with some of the knox features (secure folder, samsung pass etc) never having used any before due to using rooted devices.
I did find a few forums that appeared to mention ways to sort of do this, where the receiving device needed to be rooted (in my case the gs6) and the sending one did not need to be rooted (gs8). However, I cannot find them anymore, they were rather old (2015 I believe) and weren't descriptive enough or easy to follow in order to get the job done... So round-about-way of saying/asking... I think we are looking for the same thing, correct?
Wish/Help Request (summarized): use old android device as chromecast/fire Tv (rooted gs6) connected to "dumb", no wifi, HDTV // using newer android device (gs8) as the remote/casting device (chromecast) or as the Fire Tv remote if going that route is possible also... SOMEBODY, PLEASE HELP US! <Many thanks in Advance!
-E.Almighty777 (I've got that god-complex ;-P )
Click to expand...
Click to collapse
Sorry, this is not at all what I am looking for. I am looking to repurpose a tablet itself to be the device displaying the video, is if it were a tv/Chromecast single device combo. It would be a small screen, yes, but it is the best way I can describe its function.
Ty
werelwolf said:
Sorry, this is not at all what I am looking for. I am looking to repurpose a tablet itself to be the device displaying the video, is if it were a tv/Chromecast single device combo. It would be a small screen, yes, but it is the best way I can describe its function.
Ty
Click to expand...
Click to collapse
I understand, and in a nutshell that is exactly what I would need to do with my galaxy s6. Repurpose it as a Chromecast , it could then play things on that screen or the big one it's attached to.. however, I guess mine requires a little extra.. as I believe you would just need this to get done what you need:
https://forum.xda-developers.com/an...mirror-android-phone-screen-to-t3015383/page2
this app in googleplay may do the trick too: https://play.google.com/store/apps/details?id=nfo.oneassist&hl=en
I noticed there are 2 links to apps that do exactly what you want... Not too hard to come across... If you happen upon the extra step I'm needing (getting it onto the TV from the "Chromecast tablet/phone) please let me know sir!
EvanAlmighty777 said:
I understand, and in a nutshell that is exactly what I would need to do with my galaxy s6. Repurpose it as a Chromecast , it could then play things on that screen or the big one it's attached to.. however, I guess mine requires a little extra.. as I believe you would just need this to get done what you need:
https://forum.xda-developers.com/an...mirror-android-phone-screen-to-t3015383/page2
this app in googleplay may do the trick too: https://play.google.com/store/apps/details?id=nfo.oneassist&hl=en
I noticed there are 2 links to apps that do exactly what you want... Not too hard to come across... If you happen upon the extra step I'm needing (getting it onto the TV from the "Chromecast tablet/phone) please let me know sir!
Click to expand...
Click to collapse
This is much more similar to what I am looking for yes, and thank you for providing references! I'll see what I find..
Ty