Quantcast
Jump to content

[pivotCE] Putting a Touchstone in My Car: A Walk Through My Process


pivotCE

Recommended Posts

I finally put a touchstone in my car. For those counting at home (minus my almost two year departure from webOS to Android), it took me 3 years to work up the chutzpah to try the install. But I did it. What took me so long? I’m glad you asked.

Why now?

You’ve seen it done a lot I’m sure.

link hidden, please login to view
. But something always bothered me about the installs I’d seen. There were too many wires, the Touchstone was glued or stuck onto the dash using adhesive, and I always thought using the cigarette lighter (12V socket), or worse, a 3-prong power inverter was ugly (and kinda lazy).

What kept me from installing one in my car was that I told myself if I was ever going to do it, it had to follow 3 rules:

1. No wires! It had to be clean.
2. It had to be modular. I might want to sell the car but keep the Touchstone set-up.
3. It must be powered from the car’s battery or fuse box.

The problem was, I didn’t know where to begin.

The research

I knew adding power to the car was possible from stuff I’d read online. But everyone made it look so simple and I’m a car-wiring n00b. So I did what every online-savvy I-want-to-learn-something-new person does, YouTube. This video will teach you the fundamentals of installing an Add-A-Fuse or Expandable Circuit as it’s called in the video.

The other important thing to know in all of this is how to splice cables. With my time as a musician and tech hobbyist, splicing cables is pretty standard stuff. I did have to read up on splicing the USB cable that I wanted to use to ensure I could hide the cable. Google was my friend.

What I used to do it

The parts I ordered:

  •  (I actually got these from AutoZone, link for example only)
  •  (the item here now looks a little different than it did when I bought it)

The tools I used:

  • Solder/Soldering Iron
  • Wire cutter/stripper
  • Ratchet set
  • Heat shrink

Trouble spots

I ordered the Add-A-Fuse twice. I also ordered the Hardwire Barewire twice. Why? Because I never truly had it all grounded properly to begin with and I thought my parts were broken. I ordered new parts. And unsurprisingly, those didn’t work either. Until I tried a different spot for the ground that followed the instructions for bare metal in the video. Tada! Power.

I originally used electrical tape, the crimp joint that comes on the Add-A-Fuse, and left the ground wire bare. These are all areas that are recipes for disaster in a vibrating car. To overcome those areas, I opted to solder each splice and add heat shrink over it. I even coated the bare ground wire in solder to get a better connection behind the bare metal bolt.

Getting the USB cable through the holder was a pain. I tried carving with a knife, using a small dremel cutting wheel, and then finally opted to melt my way in there with the soldering iron. Don’t judge me. It worked. :D

Super quick summary on how I got power

  1. Cut USB ends off Barewire and USB angled cable, soldered and heat shrinked together
  2. Stripped loose wire end of Barewire back, snipped off crimp connector and stripped Add-A-Fuse wire back, soldered and heat shrinked positive leads (red wires) together
  3. Added solder to ground wire from Barewire and secured it to the bare metal bolt
  4. Found a switchable fuse port in the fuse box of my car and bare metal bolt for ground
  5. Popped out the fuse, installed that fuse into the Add-A-Fuse, installed a 5 amp fuse into the second port of the Add-A-Fuse and plugged it into the port in my fuse box
  6. Plugged the USB cable into my touchstone and started my car. IT’S ALIVE!

Photo Gallery

Each photo has my notes as well. Enjoy.

#webosforever



Link to comment
Share on other sites

  • Similar Topics

    • By Aventiled
      Hey
      I have an OLED C3 evo
      A Pioneer amplifier is connected to the optical output.

      I want to connect Bluetooth headphones and use them at the same time as the amplifier.
      The thing is, I haven't seen such an option on TV. It is possible to play simultaneously with the Bluetooth headphones and the internal speakers on the TV.
      There is no option for Bluetooth and the optical port at the same time.

      Am I missing something here?

      Thanks
      Dani
    • By News Reporter
      LG is rooted in the philosophy of open innovation – an open approach to innovation and facilitating collaboration to create a better life for all. These collaborative partnerships involve LG affiliate companies and extend to government, universities and research labs, with the goal to establish an open ecosystem of innovation that will benefit and empower all involved.
      Recently, the LG Toronto AI Lab welcomed 30 graduate students from various universities in South Korea to the
      link hidden, please login to view (CARTE) at the University of Toronto. The event – initiated and organized by the Toronto AI Lab in collaboration with CARTE – brought these talented students together to explore applied research partnerships in Canada and introduce them to career opportunities at LG. Sponsored by the South Korean government and managed through the University of Toronto’s Faculty of Applied Science & Engineering, the 6-month CARTE program accommodates students from a wide range of disciplines, including technology, engineering, and the natural and mathematical sciences and aims to inspire students to leverage AI innovatively in their respective fields.
      The selection for this program was competitive, drawing participants from among South Korea’s brightest. These selected students will engage in 10 industry projects, including three spearheaded by the LG Toronto AI Lab.

      Kevin Ferreira, Senior Director and Head of the LG Toronto AI Lab, shared, “Our collaboration with the University of Toronto and the South Korean government on the CARTE program aims to enhance our research capabilities and strengthen our talent pool. This event enabled us to present the extensive work undertaken at the LG Toronto AI Lab to an exceptional group of Korean students, laying the groundwork for deeper research collaboration.”
      Showcasing some of the Toronto AI Lab’s recent work, Manasa Bharadwaj, Senior AI Research Scientist, presented on behalf of the LG Toronto AI Lab’s Conversational AI team and their research into Responsible Conversational AI. The talk covered the motivation, technical details and results of the team’s 2023 published research titled ‘COUNT’ and ‘GPT-Detox’. The two paraphrasing approaches leverage unlikelihood training and prompt-based approaches respectively to convert unsafe text into safe text.

      Mathieu Tuli, AI Research Scientist, presented on the work that the LG Toronto AI Lab Digital Human team conducts, highlighting FlowFace, the team’s recent CVPR) 2024 accepted paper. The talk provided detail on why FlowFace is an important innovation for the community at large, and how it affects the rest of the Digital Human pipeline.
      Thi Ha Kyaw, Staff AI Research Scientist, presented an introduction to quantum computing and quantum algorithms in general, and why quantum is worth pursuing in the current quantum utility era. He also presented his team’s recent result on super-exponential catastrophe of quantum algorithms in noisy quantum hardware.
      During their time in the program, students will participate in graduate-level intensive courses in Machine Learning and AI, delivered by the University of Toronto’s Department of Mechanical & Industrial Engineering. They will also benefit from tailored AI support services provided by CARTE, including research and training in AI for academic and industry partners.

      Furthermore, students will have the opportunity to attend several applied AI seminars at the University of Toronto and engage with AI and machine learning projects across various sectors, including industry, government, and non-profits. A dedicated workspace will also be available to them, fostering collaboration and allowing them to apply their knowledge and skills within Toronto’s thriving AI ecosystem.
      The program will conclude in late June, where selected students will present their projects to industry partners, showcasing their achievements and the potential for future innovations in AI.
      Contributed by LG Canada
      # # #

    • By pivotCE
      link hidden, please login to view hold a number of events. This year’s will be of interest to fans of webOS phones, tablets and other computing devices of the past. The festival is held at the and runs over three days from the 12th to 14th of April. The festival includes three elements:
      – some with modifications to function in the modern environment. and . . For readers of this blog, representation of webOS devices will be in two of those areas. Jon W of the is attending over the weekend and will give a 50 minute talk at 900am on Saturday the 13th. The consignment shop will have a small selection of webOS devices for those who are interested.
      So if you are in the area, why not go along?
      If you can’t make it, you can follow along via the and TouchPads are available remotely at
      Discussion is at the . You can read more .
      Picture Credit: .
      The post first appeared on . Related posts:

    • By pivotCE
      Sooo that was a really long time since a release, but
      link hidden, please login to view are still around and active as ever! We have continued making updates and producing testing images. But a lot happened that resulted in us not putting out a proper release out in the past few years.
      Those who have stayed in touch with the community will know there has been some turmoil with the closure of the webOS Nation forums last year. Things stabilised over the last year as people converged around the and made plans on the associated . Much of the old information from webOS Nation was preserved thanks to the and can still be accessed, if imperfectly. We have now set up a that largely replicates the old layout and is ready for fresh content.
      If you are eager to find out what we’ve been working on and to try out the new release, read on…
      The (Jenkins) builder infrastructure we had available previously decided to have a number of malfunctions, leading it to be no longer available to us. So for now we’re back to our own builders for building all the images, which isn’t great, but at least we’re still building and providing images! We are now using , which means newer base components like systemd, pulseaudio and wayland.
      Since the last release LuneOS has gone through a major rework under the hood. To summarize:
      We moved from Qt5 to (6.5.2 included in this release). We have moved away from our own compositor (luna-next) to the one provided by LG in called luna-surfacemanager. We are now using LG’s WAM (WebAppManager) instead of our own custom one together with LG’s fork of Chromium (94). A major rebase of all components shared with webOS OSE to be based on the now. This included a migration to Enhanced ACG which provides a lot tighter security for LS2 calls from apps and services. This all was an enormous amount of work behind the screens but little visible to the end user, however this does offer clear benefits going forward being:
      A shared code-base with LG, which means less custom components and maintenance. Years of field tested code on LG production devices which offers more stability. In this process we were able to keep backwards compatibility for apps and services. Easier to upgrade to latest OSE components, since we have migrated almost all remaining components that were still not based on the latest webOS OSE or on Open webOS. (125 components were migrated in total, 15 components are still to be migrated). In the meanwhile we have also been working hard to support the newly released devices such as the PinePhone, PinePhonePro and PineTab2 which are affordable devices which can run a very close to mainline kernel and a multitude of OS-es. We now support booting off on Pinephone.
      The new close to mainline kernel for the Pine64 devices allows them to run things like out of the box!
      All other supported Android devices are now based on 9.0.
      So what is ahead for the near future?
      Our focus will be on the mainline devices and emulator (), however we will try to keep support for the Android/Halium based targets as well.
      Upgrade to latest Chromium 108 released by LG recently Work on audio & multimedia infrastructure provided by webOS OSE to get it working in LuneOS Work on camera infrastructure Try to get a mainline kernel working for Tenderloin, Hammerhead, Mido and Tissot. Improve/add QML components and add new basic apps to be used such as Camera, Flashlight, Audio Player, Video Player Piggyback off some of the work done by the . Provide a GSI image for newer Android (9.0+) based devices, this would allow a standard image to boot on most modern Android devices v.s. building a device specific one for each device. Known issues:
      Battery usage is on the high side No audio in webapps (we decided not to spend time on this, seeing we plan to update Chromium soon anyway) The Usual:
      Sign up for. Get involved and [ UPDATE https://pivotce.com/2014/09/22/webos-ports-help-wanted/ ] Feel free to download the updated builds to get started. Currently supported targets: PinePhone, PinePhonePro, PineTab2, Qemux86-64 (Virtualbox), all with mainline kernel. Tenderloin, Hammerhead, Tissot, Mido, Rosy, Mako (Android 9.0/Halium based with their respective Android kernels (3.4 and newer)). RaspberryPi 3 and RaspberryPi4 might work too, however we haven’t tested this ourselves.
      . And remember we don’t do timelines.
      Don’t forget to contact us with any questions and feel free to join the discussion on the . Catch us on Twitter @webosports on IRC: Libera:#webos-ports, or email [email protected].
      We will see you shortly again with a new release!
      Picture credit: from Pixabay
      The post first appeared on . Related posts:

    • By pivotCE
      The webOS community may be a bit smaller these days but it’s no less devoted to the platform. WebOS Ports is a small team of developers. As you can imagine, it is a few people to maintain a full OS that consists of thousands of components. Things are starting to come together for LuneOS, with the current major rebase and stable release. But we still need your help.
      As nice as it is to have some additional folk contributing, developing, and working on issues, we still need more developers to get involved to make this community project really take off.
      “Our focus is core functionality”
      We cannot stress enough that we are building an OS focused on core app integration that is simple, beautiful, and user-centric. Right now, function comes first. If we had a penny for every developer that knew some web code and could make a beautiful static mock-up of an app that didn’t do a thing in the backend and then said “I did my part, it’s up to you to make it work”…well, we’d have a lot of pennies.
      Developer requirements
      Once core app integration happens we will need HTML/CSS smart people. But to be an asset to the team, you need to have a good grasp on any or all of these technologies:
      Javascript C node.js C++ QML Qt Yocto Graphics design Are you decent at some of these, but might need help from time to time? That’s fine!  We’re a community, remember?  Hit up the
      link hidden, please login to view and/or channel and ask! Get the bugs out!
      We have several applications already available but many are placeholders or have basic functionality. Some of the apps are almost fully functional like Settings. But even Settings has bugs and can use refinement.  OK there are bugs everywhere! (If only it were as easy as a can of Raid to fix them)!  We’ve received lots of questions about how to get plugged into the project quickly.  Easy! Head over to our  to see current issues. Find an area where you think you can help and then find us on or (see below) to talk about it.
      Some examples of areas that need bug fixing are:
      Email: Some minor bug fixes Settings: Add Settings when needed Phone: Further polishing Calendar: Google C+Dav integration needs updating to adopt for Google’s changes Browser: Rework UI to be more webOS/LuneOS like And more. Core Apps/Features/Backend magic
      The Open webOS project released several core applications that were Enyo1 based.  These apps are in LuneOS
      Messaging: Needs a rework or rewrite to give proper functionality similar to legacy webOS PDF needs converting to QML. LuneOS also needs a media player app (maybe reuse/rework the webOS OSE app for this?). The C+Dav connector is there, but it needs updating for various changes by Google. It also needs testing for other providers. Additional IM connectors would be good to implement (Telegram, Signal) etc, there are existing plugins exist for Pidgin/libpurple that can be used. Looks aren’t everything
      As you can see, to really make stuff work first, most of what we need is in the backend.  It’s the old battle between form and function. Which comes first?  Designers will argue form!  But Ports is focused on the core functionality that has to work first and look pretty later. It’s a hard pill to swallow and we get that, but when building an OS, it’s the most important thing. If it looks pretty but doesn’t work, the project loses potential users. If it works but doesn’t look pretty it will at least show promise and that encourages positive feedback. And with a community led project, if you don’t have good feedback you’ve already lost.
      Additional help wanted
      Ports is looking to expand our public relations presence. If you are located outside of the United States or more specifically speak a different language than English and would like to help us advertise and direct interested people toward LuneOS and WebOS Ports, please let us know.
      We are also looking for a WordPress “expert” for a new site we’ll be setting up soon. Are you good at making tutorials?
      We have several “How to install LuneOS guides” on the wiki. If you’d like to make friendly guides, that’d be great!
      And finally, we need a “wiki-meister”. Someone that really knows the ins and outs of running a mediawiki!
      Get involved
      Everyone can help in some way. We need testers and bug reports! Sign up on the , contact us to let us know that you signed up and what your username is, and we’ll upgrade your account so you can post issues.
      Developers please join us on and/or drop by the IRC channel
      How to Contact WebOS Ports
      Want to get involved? Have a question? Get in touch with us.
      [email protected]
      Twitter: 
      IRC (Libera):
      Telegram:
      Issue Tracker: 
       User Support Forums
      Join the forum .
      The post first appeared on . Related posts:

×
×
  • Create New...