It comes down to the fact that it's not what it is designed for but it us ultimately up to you what you want. Additionally, tablets have gloss screens which can create dangerous glare and reflections while headunits have matte screens to combat that. LCDs also don't like to be left in the cold. Most tablets even come with warnings not to leave them in direct sunlight. These don't fair well with extreme temperatures like the inside of a car on a sunny day. most likely a lithium polymer pouch format. A majority of the device itself is a lithium battery. ![]() The reason I mention longevity of a tablet is the environment. Plus with a dedicated nav/receiver, you maintain the amplification, AM/FM tuner and they don't require custom mounting or fiberglass bezels. They don't come with bluetooth and tethering and all that crap because it's what gets people killed trying to fiddle with settings. I suggested purpose-built receivers because they are designed as a non-distracting interface that's simple to navigate, switch radio stations and skip songs. Android typically requires precise touches for opening Apps, entering information, accepting dialog boxes, changing settings, etc. The basic Android interface is not designed for use while driving like the second video's ELA interface. Then you can use it other places than just sitting in your car. Its primary function while driving would be music and navigation which are things a stereo and a gps already do just fine. Regardless of how many cores or apps it has. My quick negative reaction is based on that I don't feel like anyone needs an Android device while driving. Or if your headunit has an aux-in, you could relocate it hidden under the seat or in the center console if you are trying to keep cost low. If you get a small amp you can just run the headphone output to the RCA input of the amp. There's no reason you need to bluetooth the audio to your headunit. If it's something you're set on doing, I would suggest figuring out if relocating the stereo is something you really need to do. The second vid with the custom fiberglass bezel and custom interface is however very cool. If you want to do it for the cool appeal, that kills it right there. I just think it looks out of place especially the implementation in the first video with the cutout on the edge and the weird plastic buttons sticking straight up for volume. Try keeping an open mind from time to time? Might do you some good. You guys sure judgmental about this man's appearance. So in the end my only concerns would be the mounting for both the tablet, and the head unit. I have a passionate dislike for anything apple makes personally. Many many people do this with iPads, but you don't usually see it much with androids which is why I find this interesting. ![]() Not like you're going to drop it when its mounted. I highly doubt a tablet would break after a year while using it properly. I would get one with wifi only and use my phones 4g tether to give it data. Also I wouldn't get a data enabled tablet. It just seems to be a good shape for a single din head unit. The mounting I do wonder about, and I haven't looked behind the vdc to see the depth. You can get a $200 tablet and have more features than most 7 inch double din head units that are generally around the $500 range. ![]() I really don’t want to have to rebuild DD from scratch.Well I already have a head unit that has a2dp bluetooth audio streaming so I can already use my sgs3 to stream audio, but I like the idea of this. (Instructions for my situation have been updated above)ĭoes anyone have any thoughts on how to correct this. But on my setup, all I can say is that the 6 steps above have me up and running when going from HA 2022.6.7 to HA 2022.7 and DD 3.1 to DD 3.2)ĮDIT: This looks to have not worked (the order), I have been met with the below on DD after home assistant restart.ĮDIT 2: This was corrected with a redownload of 3.2 while on HA 7.6 and a restart. (Maybe if I would’ve updated HA to 2022.7 first, restarted, then installed DD 3.2, restarted, things would’ve worked properly. Save a copy of the Dwains Dashboard folder from config to a safe place. To make sure I understand correctly if I am now on 2022.6.7 and DD 3.1.īelow is what worked for me: → maybe I did things out of order but I can say DD is working coming from 2022.6.7
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |