Related
Hey guys, I have searched high and low for a solution to this problem but have come up empty so far. I just got a joying head unit and everything, including the easy connected app, seemed to work without issue. I decided well since I had the headunit running next to my pc that I would flash Malaysk's custom rom before installing it. After that, I reinstalled the app from various sources including the oem app but none of them seem to allow me to connect my same exact devices anymore.
Why is this important for me? I had planned on controlling a tablet in the back seat for my son who is still to young to put on show without trouble. Essentially, this would allow me to never have to reach back there to help him out.
I have read, from joying, that it would no longer work after flashing new firmware but that seemed to not be the case from some things I had read here (please correct me if I am wrong on that). Tried different cables and ports but no luck. I did read that a license might need to be carried over but not sure what that entails as I can find ZERO info on this easy connected app/problem. I hope that this is a very simple fix and that I did not jump the gun again for the chance to flash a new device (its addicting and I blame XDA for my problems...).
I did try and find some other apps that might allow me to do the same thing. RemoDroid seemed promising but didn't function. Most other ones are meant for controlling from a pc or browser and just weren't useful for the task at hand. I am open to solid suggestions. I use all Android devices and avoid the Apple juice. Any insight you guys can offer will help a tired Dad out. Thanks!
Edit: Solved-ish
The easy connect app seems to function now intermittently. Not sure there was a specific thing that I did to fix it. Seems to work when I launch easy connect app right after booting up and nothing else. Messing with other apps seems to cause a problem for my devices. Also, switching between my devices(phone and tablet) may also have been causing a problem, not sure yet. I suppose I'll just keep trying to make it work reliably until I break it again.
On the previous version of the easy connect app, you were able to disable Drive Mode from launching. Not so on the newer version with Android WiFi. If anyone has a solution to that I would appreciate it as the Drive Mode app is useless for my needs.
Note 4 - USB - works great. I have yet to try over wifi
Note 10.1 N8013(lollipop rom) - USB/Wifi - works great (disable smooth mode, remote device screen cannot be turned on with easy connect "Home" button)
http://forum.xda-developers.com/and...1024x600-rk3188-joying-try-uploading-t3262030
I tried several different apk's but they all have similar results and end with a connection failure.
I haven't yet tried going back to stock firmware so that might be worth trying. I installed the headunit in my car so I'm not as willing to keep flashin it as I have to park down the street from my house.
So not sure what magic I used but I was able to get it working for a moment and then it stopped again. USB and Wifi android mirroring were working so I know my current firmware/setup is functional!! Once I got it working I started configuring some other apps and when I went to run it again it wasn't connecting. I guess I'll just keep messing with it until I can figure out what got it working again.
With the newer version of the easy connected app, I can no longer disable launching of drive mode on connect. Is there a way to disable that option with the 1.4 version?
Hi.
Is it possible mirror in wifi with android?
Can you explain the way?
Inviato dal mio SM-G920F utilizzando Tapatalk
I have a 1st generation XBox that only has an Ethernet port. Is there a way to connect it to the Fire TV to get it access to my network through WiFi?
When Ethernet port is plugged in it disables wifi connectivity. after that a bunch more work making wifi the default gateway with routing... if it is possible. . prolly worth your time to just spend the $30 on an adapter for it or install dd-wrt on an old router you have laying around. . I had a similar request where I wanted to know if my firetv can double as a coffee maker but no-one has solved where to put the k-cup.
Its not so much the device in this case that is unfit for the purpose (well - unless it is, as described above.. ) - it is, that the minds that are interested in and forming around solving those problems are working on much better (reputation) and wider known projects - AND the devices they support cost anywhere from 10-30 bucks used already. So dont tell them why you bought a Fire TV instead.
I know that current "technophiles" see the world as app based solutions that will come to them if they ask around often enough - but really, we already are at the minimal knowledge and minimal cost stage - and they are in essence complaining about convenience.
I have a problem - and see the solution in this one ethernet port another device I bought already has. Let the internet work out the rest, I am waiting for my app - its already rooted, how hard could it be.
And thats not how this works.
First of - why should they be working on an app based solution? A functionality layer if you will - if they dont have control over the entire ecosystem and networking, I heard has something to do with security. Sometimes. And with devices that have to work longterm - quite unlike the little plastic box that currently sits under your TV. And that today is rooted but tomorrow might not be - because, well its not yours to decide. Entirely.
dd-wrt and openwrt are what you are looking for - but that was already mentioned by the person posting before me.
I'm just here to explain why the "asking for a service" mindset ultimately breaks, when it comes to open source movements. Especially when your demands get more and more specific. ("I have bought a...")
I can say all this, because I currently use ddwrt to service some of my needs and it works perfectly well, creating all kinds of synergies I actually actively use - many of which actually are real enablers for owners of Android based Kodi boxes.
Well - then again, it might actually work already... (Turn off WLAN in the gui, then enable it via the shell (maybe that way both can be set active at the same time) and start configuring iptables).
http://forum.xda-developers.com/showthread.php?t=444004
But understand that this would be very much a hack. So usability, interfaces, security concerns are not on the forefront of peoples minds. Also - have fun configuring ports that way (ftp mostly I suppose.. ) - if you dont want everything to be open.
Google and 2 minutes - btw.
When you read through the thread you start to recognize - that what you are actually looking for is implementation and support (Hence dd-wrt or openwrt). Also - it becomes very clear why this probably never will become an app (needs root, needs to install a new library (think of stuff only busybox does as a core function on android - this has to be vetted not to cause unexpected problems), still only circumvents Androids core functions (either ethernet OR wlan), isnt fully featured, and most of all - most technically inclined people who actually need the functionality simply buy into the dd-wrt or openwrt ecosystem and its all there already).
So to break it down to a few sentences - if you get a person willing to establish a very specific function for his/her own purpose against prior design on an open source OS, you are golden. But, you wont get them by randomly asking around for help on an internet forum. And dont expect to get entire featuresets or usability options alongside it. If you want those - and you do - go with the communities that are known for solving those problems and buy into the devices/ecosystems they use. 10-30 USD should be well worth it.
But if you are in a hacking state of mind - go for it and make those devices work like you want them to.
I have a FTV2 rooted to 5.2.1.1 using the guide at atvnews. I have installed Kodi and configured it to my liking. Im using HDMI cable to connect it to directly to my Harman Kardon AVR-154 input HDMI3. I have used this port for other devices and I can get surround sound so I know the port works on the receiver. Im also running Kodi 16.2 Jarvis.
Anyhow, I cant get digital audio to come through my speakers from the AVR unit. I have sound coming out from the TV. My TV is a Samsung unit, it has CEC enabled and it locates the FTV2 unit.
I have logged into Kodi and enabled pass through and enabled digital receiver option as well. On my receiver, I have HDMI3 selected and regardless of the digital output option selected, there is no audio coming out of my speakers when a movie is being played. Is there any option or setting I can change to get this working?
When I checked audio on the FTV its set to Digital Output through HDMI.
Finally, another issue I am having is the original remote not being able to be paired with my FTV2. Im using a USB hub, so I have a physical keyboard connected to it and am able to navigate through the menus this way but would like to have my original remote working. I have tried the system options method and its not working.
Any suggestions to my two issues?
google firetv kodi sorround (first result on xda, even has pictures)
google firetv pair remote (look for the reddit thread)
Also, don't expect anyone to care that you connected your FireTV to HDMI port 3, and that your AV reciever outputs "digital audio" to your speakers (doubt it), or which Harman Cardon receiver you bought. Chances are you will not find anyone in here with the same setup to be able to replicate your issue, so you have to start thinking and breaking down the issue yourself.
The internet is not a free support tech, that will stand in you living room and mutter "have you tried port 2 instead":
It s the "can someone fix my home router" issue all over again. Connectivity issues are hard to "phone in solutions for". It is your responsibility to try to understand and solve them, not ours. Never expect custom made solutions for your equipment, your port configuration, and so on. It's not going to happen.
Other people troubleshooting your issue (I'm refering to the xda thread I'm having you look up yourself) have installed different Kodi builds (SMPC) and even switched AVRs to pinpoint the issue. Maybe try some of that yourself. (After reading the thread I am refering to).
Also - use google. Keep questions at least somewhat concise. Show that you have tried to tackle the issue yourself (including google). If your remote turns out to be broken (in the reddit thread you find the button press thats needed to put it in pair mode), don't ask XDA for help, thats a product support question...
ALso, nothing of what you describe has anything to do with being rooted, so the title is misleading.
Hopefully a bit more useful then the post above.. (If thats all you had to say, then, why bother responding in the first place?)
1) To the Remote.... AFAIK the Remote that comes with the AFTV2 is some 802.11 WiFi job that only works with the AFTV(2)? It is NOT to be confused with the older Bluetooth Remote (AFTV1), which as I understand does not have the Mic on it. Sadly I have the latter Device, and the way to pair it is to depress the Home Button for 20s. Yes the on-screen instructions say 10s but in my experience that's BS! You'll know that the Remote is pairing when the throbbing white light turns yellow-brown. Before going back to white, and disappearing all together.
As to your Audio Setup... Have you made sure to go into System > Settings > System (Making sure to have activated the 'Expert' Settings level), then; Audio output
Number of Channels - 2.0 (Yes this must always be 2.0 for everything to work!)
Enable Passthrough (Obviously)
Dolby Digital (AC3) capable, and
-Enable Dolby Digital (AC3) Transcoding
This may be the cause of your problems. In short you have to enable this IF you have an older Amp such as myself which does NOT support PCM Multichannel Audio. (Something which is AFAIK only available over HDMI e.g. Dolby HD & DTS-MA*), you will NOT want to enable this. Otherwise if you have to use the older S/PDIF (Optical or, Coaxial), to drive your Amp, in my case though my TVs ARC (Audio Return Channel), e.g. the S/PDIF Out is on the TV. Then you must enable it their.
One other note here Depending on your TV, you may also have to troll though the Audio Settings there and, locate the Digital Out Setting (Or whatever passes for that Setting on your set.), and either set it to PCM, or Compressed. In my setup it has to be compressed for DD/DTS to work
DTS capable receiver should probably also be ticked.
Now to test it...
I would recommend you find the Big Buck Bunny Add-on, since it covers a broader range of parameters. Resolution, 3D, Audio Formats which seems to be your chief concern here. I could also just toss out their that IceFilms also has mostly 720p HD Shows, and Movies as well and more often then not also in DD5.1. though the latter is less shady then the former, even if it's less practical. But, unless you have some idea of where to find HQ Stuff with DD5.1 or DTS, then chances are it will certainly only be an AAC 2.0 Stream. Which of course will never be in Surround.
*If your AMP for NOT support either DD-HD, or DTS-MA, then it may be safe to assume that it also doesn't not support PCM Audio either. In which case you'll need to readjust your settings to use the S/PDIF settings instead.
Congratulations, you just spelled out the entire posting I suggested the OP googles for once again, in regards to the correct pass through settings.
(To be fair, you went into more detail regarding PCM Audio vs other Kodi Audio options, than even the original thread.)
You spelled out that to re-pair the remote, you have to press the home key for 20 seconds. Which the OP would have learned by googling firetv pair remote, in five seconds on their own.
I do not assume the OP is struggling with a Fire TV 1 remote, also - the AFTV2 doesn't have a SPDIF out anymore.
To be honest, somewhere after "I rooted my Fire TV", "I put the cable in HDMI 3", and "my Harman Kardon sends digital audio to my speakers" - I lost all patience with the a guy that needed Kodi settings he could have googled in 5 minutes and an instruction on how to get the remote into pairing mode, which he could have googled in 5 seconds.
You are a better man than I am - I would have liked to see the OP go the long route to get to the same answers...
---
Two other nice things to learn from this:
- Make the posting title descriptive, and not the first thing thats comes to your mind, or a bait and switch that ultimately has nothing to do with your question. Other people might search this forum for the same issue - and a descriptive title helps them not to have to ask the question again, and that means that we don't have to answer it again - because presumably most people can be asked to google an issue, before resorting to a personal help request.
- Show that you took some effort to pinpoint the issue first. If your request starts with a description of your living room, something urks me as being wrong. Don't name your AV reciever, but take the time to learn which audio standards it supports. Don't state, that the Fire TV hangs on HDMI 3 - but take the time to test the other HDMI ports so you can exclude that one as the cause of your problems..
Basics.
Also - leaning how to do basic troubleshooting using google on your own - isn't necessarily a bad thing, because the next time you won't be describing your livingroom to people on the internet again, if you should have a different issue.
Don't assume, we like doing the legwork (what audio standards does his receiver support, yes - lets play Amazon support and tell him how to pair his remote (because of course you didn't consult the manual (page 43 btw: https://s3-us-west-2.amazonaws.com/customerdocumentation/Amazon_Fire_TV_User_Guide.pdf ) or google).
I did use google and even reddit and was recommended to come here by someone.
I wasnt looking for a step-by-step guide, merely if someone else had a similar issue. By pointing out my hardware, perhaps someone ran into a different issue with the same make or even model of AVR unit. But I was simply hoping for some direction or what I could check and test for.
I simply asked for insight or what I could look for, not to have a reply that really wasnt necessary.
And by mentioning root and HDMI 3, you set the perimeters to make sure that, ...
Its ok - you won.
Someone did provide a detailed solution.
Just understand, that if you had found the surround sound settings topic before, Ichijoes explanation would now possibly be visible there, where future users would find it more easily. In a thread named "Im rooted and have two issues" - they probably won't look.
Also, just as an aside and not meant as a passive agressive poke - AV recievers have to be interoperable with other equipments. Thats where standards come in (which audio standards does mine support, which audio format do I want from Kodi...) -- so it actually is worth the time to "learn them". They basically are what also the manufacturer is "betting on", so he has a market he can sell into.
The chance that someone also owns the exact same equipment and has solved exactly your problem before, and now happens to see your thread - is always very low with all interoperability/connectivity stuff. Understand that there are maybe a dozen of people floating around in a forum like this who can and might be willing to do even basic trouble shooting for you. Maybe 100s if you add the educated lurkers out there who might chime in, when they see an issue they have solved in the past.
Thats your "pool" for the off chance - "maybe you have the same equipment and issue as I do" bet. And usually it means, that you arent successfull with it. Now if you just ask the standards question (even on the level of "I cant get surround sound - what could be the culprit") your chances increase manyfold.
So whenever I see a "i have a A and a B, and they don't work - I've already restarted the device" usually not only does it read to me as "doesn't know the basics", it also screams "doesnt wan't to learn, wan'ts product support". Now while this is a product forum (and XDA also sees the people in here as a product support community) -- people in here usually don't see themselves as product support assistants.
Again - not saying this in an aggressive tone, this is the post-battle talk - about details that will eventually be lost, when this thread leaves the first pages.
Standards matter. Showing that you'd much rather "learn" than to get your problem solved matters as well. At least to me... But then, what do I know...
So friend gave me a FireTV Stick, brand new (Fire OS 5.2.6.3 (606754020), Fire TV Home Version 6.0.0.6-127).
Little desire to deal with Amazon, need to enable USB Debugging & ADB. Gotten as far as Fire App on Phone to bypass Registration to get to Settings-Device-Options, held Center/Down to Enable X-Ray, Developer Options Hidden Menu etc, but can not find any way to Access USB Debugging or ADB to enable them. When you enable Developer Options, only thing it does is give option clear Recorded Metrics whatever. Enabled it, rebooted, disabled it rebooted, re-enabled etc etc, only option I get is to clear recorded metrics.
Tried several diff ways, nothing can recognize it ADB as I can't enable it, tried USB to PC, it recognizes FireTV Stick, can see whats on the Drive or SD Card, but again, can't send files to it without USB Debugging. Rooted every Android Toy I own, not new to this, but has me stumped.
How do you enable USB Debugging or ADB to a FireTV Stick with latest OS without ever Registering it? As far as Normal stuff, it hooks to Network fine (behind Firewall & VPN), but won't Update, why if you go with the Fire App on phone, you can "pair" and get as far as Option to Access Hidden Developer Options etc, but no USB Debugging or ADB Enable Option is there.
Never messed with one, was more a sort of Gag Gift for a favor he owed me, so said why not, lets see what all the fuss over these things is, I wanna tinker with it.
You can always de-register the device from your Amazon dashboard after setting it up for the first time.
I remember reading in another post, someone describing the exact same situation.
Using the app to skip registration and discovering there was no option to enable adb debugging.
Sounds like they may have fixed that.
I noticed in 5.2.6.3 the same security feature Amazon has implemented to detour people from buying and selling blacklisted devices. I have spent more time than I would like to admit trying to find a loophole, but without the ability to enable abd and unknown sources it seems impossible. I hate to say this but Amazon has it locked down and if anyone could figure it out they would have to someone on xda but no one I know has jad a clue. I don't condone theft one bit, but love a challenge and this one has me stumped.
Well, part of the fun, lol. Voice in my head keeps saying the Fire App, has to be a way, but not seeing it as yet. Did read where someone built a special HDMI setup and over loaded the OS, prompting a a "bootloader" screen and got in that way somehow, but far beyond me and said the parts to build it were like $150, let alone knowing what to solder to what etc, beyond my capabilities.
matafact said:
Well, part of the fun, lol. Voice in my head keeps saying the Fire App, has to be a way, but not seeing it as yet. Did read where someone built a special HDMI setup and over loaded the OS, prompting a a "bootloader" screen and got in that way somehow, but far beyond me and said the parts to build it were like $150, let alone knowing what to solder to what etc, beyond my capabilities.
Click to expand...
Click to collapse
Honestly its fun and has also become consuming trying to find any way to get past each screen lol. I heard the same voice in the past and it worked lol. Now with these 5.2.6.3 2nd gen firesticks I have no way to get to Dev options and with the 4k firesticks it says my login is incorrect to Amazon, and as I previously mentioned I am pretty much out of ideas. Overload HDMI huh? Sounds interesting. Well back to the drawing board for now and If I learn anything I will let you know.
Well, Fire App in my head, dont know why, just keeps coming back to me. Not a programmer, not a Droid, Hacker type, but thinking this way, feel free to tell me Nope, won't work and this is why.
How does it pair with FTV Stick etc? Not Bluetooth etc, so how does it connect? Possible to take Fire App and tinker with code, add some/modify code or a script etc to modify it and get further into FTV OS 5?
Or thinking again, don't know, but seems with a Laptop on say WiFi Network, just like Droid, Iphone, with a Virtual Machine, know Virtual Box you can set up about any Android setup ya want.
So setup a Virtual Machine, tinker with Fire App in some way, and if Laptop can connect to FTV , well, just idea in my head that must be away to get around it, or at least with a Laptop would open many more options to try & beat it. Havent tried this yet, just keeps floating around in my head, may not even connect to a Virtual Machine, maybe over weekend I'll tinker with that a bit.
Somebody who programs etc would know far more on topic, but same idea keeps bouncing around in my mind. Could be dead wrong, maybe they have that locked down to, but guys here, well, how many "can't hack" toys have they already beat, lol.
matafact said:
Well, Fire App in my head, dont know why, just keeps coming back to me. Not a programmer, not a Droid, Hacker type, but thinking this way, feel free to tell me Nope, won't work and this is why.
How does it pair with FTV Stick etc? Not Bluetooth etc, so how does it connect? Possible to take Fire App and tinker with code, add some/modify code or a script etc to modify it and get further into FTV OS 5?
Or thinking again, don't know, but seems with a Laptop on say WiFi Network, just like Droid, Iphone, with a Virtual Machine, know Virtual Box you can set up about any Android setup ya want.
So setup a Virtual Machine, tinker with Fire App in some way, and if Laptop can connect to FTV , well, just idea in my head that must be away to get around it, or at least with a Laptop would open many more options to try & beat it. Havent tried this yet, just keeps floating around in my head, may not even connect to a Virtual Machine, maybe over weekend I'll tinker with that a bit.
Somebody who programs etc would know far more on topic, but same idea keeps bouncing around in my mind. Could be dead wrong, maybe they have that locked down to, but guys here, well, how many "can't hack" toys have they already beat, lol.[/QUOTE=matafact;78395384]
I wish I knew how to use tasker. Im a newbie but your ideas are great and have me thinking the remote app is the key, but it is a task I do not know how to execute.
Click to expand...
Click to collapse
Hello All,
I'm new to this forum, so I'm not really sure if this should be general, dev, or just a technical question. Also I'm a software dev, but am not too familiar with android other than lightly using Android Studio for app dev.
Basically my problem comes down to this. I use a custom OpenWrt device as an ethernet dongle for my laptops by loading the g_ether driver. I would like to do this for an android phone as well. Right now I'm trying the s20 and s22 (pretty sure whatever solution I come to will work for both); however, when I plug my dongle in, the phone will see the dongle with all the correct device descriptors and all that, but will not connect and attempt to get an IP.
My current guess is that the phone just doesn't have the right drivers on there (cdc_ether or cdc_subset), or that it is not loading them.
Thus far I've tried poking around with termux, but have not gotten too far. I was hoping this community may be able to help me figure out how to get the phone to use the dongle.
Lastly, would really rather not root the phone unless completely necessary.
Thank you all for any advice!