Forum Replies Created

Viewing 15 posts - 1 through 15 (of 56 total)
  • Author
    Posts
  • jerwam
    Participant
    Post count: 62
    in reply to: test image #3376

    The device basically hijacks AA to work. Once it is plugged into the car, you’ll see the Android Auto indicator on your stereo. You click the AA button, and it loads the CarDongle. From there you get the basic launcher and the included apps. You can use the Play Store as normal, or sideload apps as well. You don’t get access to the standard settings app, unless you install a third party launcher, something like Car Launcher pro.

    I didn’t end up going out over the weekend, but I’ll try and trigger the Google Assistant later today. My one and only USB port in my 2016 Ford Focus is in my center console as well, so we’ll see if it picks up anything.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3371

    Android Auto is pre-installed on the device, mainly due to it needing the app to function properly. One thing you cannot do is try to re-use it while it’s already in use. I tried to click on the AA app while it was connected, and it just drops you to the main launcher again.

    I haven’t tried Google assistant with it yet, nor have I tried any steering wheel controls, I can do tomorrow on my next trip. Report back afterwards.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3348

    Yeah, the firmware was pretty much the same, including the built in apps. I did see a new sitting under GPS, instead of the one that said something like “Use Phone GPS” it now says “Use Car GPS” I don’t have built in navigation in either of my cars so I can’t test how well that functions.

    The physical design of the device is different, in that it’ll be harder to open for anyone that soft bricks their devices. I know there was some documentation on what to do with the v1.0, as in opening it up, shortly a couple of pins, etc. – but that isn’t going to work with these 1.5 devices, at least opening it is different. I’m not sure if this is my official v1.5 device as the hardware specs aren’t what I ordered, so I don’t want to try and open it.

    One of the main reasons it’d be good to have some sort of button or trigger to set that off. I’m not sure if it can be done via firmware or not. I know some android applications can do it, but not sure how that’d work with these CarDongle devices. Most of the time they’d need root access, and I don’t think any one has been able to root these devices yet.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3342

    Looks like I was right, they merely built out the lower spec’d units for testing, so possibly the first 10 going to the beta testers. Once they officially go into production, they’ll have the proper specs. I guess that just means the 10 beta testers may need to ship the beta v1.5 devices back to get their proper ones, but I’ll confirm that once I hear more.

    As far as things people want tested, let’s start a list and I’ll do what I can to get them crossed off. The first suggestion I’ll make to the CD team is to have a button that triggers the recovery process. These new devices seem a bit more difficult to open compared to the older units. So it won’t be an easy thing to short the required pins.

    • This reply was modified 4 weeks ago by jerwam.
    jerwam
    Participant
    Post count: 62
    in reply to: test image #3337

    Hello Tommy, Any word on the lower specs of the v1.5 I have? I haven’t gotten an email back from your team, nor has anyone mentioned the lower specs on the Indiegogo site. I ordered the Octacore 4gb RAM and 64gb ROM version, but the v1.5 device I am testing is only a Quadcore device, with 3gb of RAM and 32gb ROM.

    The difference in hardware specs is noticeable, so hopefully once the true 1.5 devices are released I’ll get something similar to the one I ordered. Can’t imagine you’ll have a lot of happy customers once they receive a lower spec’d unit then they purchased.

    Hopefully you can get me an answer.

    Cheers.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3328

    They haven’t gotten back to me on the hardware side of things. I combed through their Indiegogo site, and I didn’t see any mentions of the lower specs being in the v1.5; so here is hoping they only built this particular v1.5 with lower specs to confirm the GPS is working. I’m sure it was a little cheaper to manufacture.

    All of their marketing material still calls out the 8 core CPU with either 2gb/16gb or 4gb/64gb – it’s even on the bottom of the box they shipped the v1.5 in, so any cost savings on dropping the hardware specs would be eaten up by the cost of rebranding all their materials.

    Once I hear from them, I’ll post an update. I’ve also asked them to improve their forum as a whole, so they might look at using wpforo.com instead.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3325

    GPS Update:

    I further tested Google Maps on a longer drive, 45min, and I can say it worked as expected. In town the GPS wasn’t spot on, so a couple of times it thought I was a street to the right, so it kept trying to re-route me back onto the proper route, but that is expected when I’m in between a couple of high-rises.

    Fred, I did test out your offline Sygic navigation app, and it does work quite well. It downloaded the local maps, and was able to properly route me to my local Mall.

    When it comes to re-routing, I can say Sygic was the quicker of the two, I’d assume that is because Google Maps needs to reach back up to the cloud and use WiFi/the CPU/RAM in order to re-determine route. There was a couple of times Google Maps took roughly 5min before it was able to get me back on track.

    It is hard to say if GMaps took so long due to being out in the sticks where my Cell didn’t have decent coverage, or if we can solely blame the drop in cores/RAM that is in the v1.5 device.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3321

    Hardware update:

    I just noticed a couple of things in regards to the SOC on both devices, the v1.5 device I have is of lowered specs in both cores and RAM. The v1 device is a Helio P22 with 4gb of RAM and 64gb of ROM, where the v1.5 device I have is a Helio A22 with 3gb of RAM and only 32gb of ROM.

    I sent an email to the CarDongle team to check into this. I’ll update once I receive word. I was wondering why the v1.5 device wasn’t as snappy as the v1.0 device is.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3319

    Bluetooth Update:

    Looks like the v1 device does see more things to connect too, but it has the same connection issues when it does connect. The v1 device can see the two different Chromecasts I have on this floor, but the v1.5 device only sees the Surface it’s plugged into, and not the Chromecast devices. Even though one of the Bluetooth devices is located in the same room. So it looks like there might have been a sacrifice on the WiFi/Bluetooth end to get a better GPS antenna.

    Not sure why the settings app doesn’t keep things connected, but that’s how things are I guess.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3318

    Hello Fred. I’m using the launcher Free Car Launcher, and it has its own settings app that can connect with the proper settings of the Android OS. I have a couple of pictures of what the Bluetooth settings looks like in the OS, but this forum isn’t the easiest one to upload pictures too. As you can see from the start of this forum 🙂

    It does appear to pair to things, like it’ll connect to my Surface Pro 6 via Bluetooth, but when I exit the Bluetooth menu and go back to it, it shows nothing is connected via Bluetooth. I go into previously connected devices, it shows the Surface, but it won’t re-connect until I forget the Surface from the CD, and forget the CD from the Surface. At that point I click on connect, my Surface prompts that something wants to connect to it, I hit allow, the CD connects, then when I exit the menu, and go back, it doesn’t’ show connected.

    It might just be the settings app not having the proper access to the device, but who knows for sure. It’d be nice to have access to the bootloader so we can flash different roms to the device, but for now I’m just living with a different launcher.

    I’ll test the same on the v1 device and see if it behaves the same way.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3315

    WiFi update:

    I tested both units in my car, just in the driveway, and I can confirm the v1.5 won’t connect to my home WiFi, where the v1 device does. The v1.5 does connect to home WiFi at my desk, using Mirroid, and it connects to the cell WiFi while in the car, so I think that is a fair trade to have a working GPS antenna.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3312

    Quick update:

    I was able to connect to my ODB2 adapter, but only inside the Carista app. Outside of that the CarDongle didn’t show it was connected to a Bluetooth device.

    WiFi seems weaker then it did in the v1 device, sitting in my driveway it had a hard time connecting to home WiFi, but it connects fine inside the house. I think the v1 device connected better to home WiFi from the driveway, so I’ll test that tomorrow.

    I didn’t do any testing on video playback is streaming yet, stay tuned for that.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3311

    The only major change from the v1 and v1.5 is a functioning GPS antenna, the rest is pretty much the same.

    I can say both versions connected to the phone WiFi, and home WiFi, although I’m not sure what side of the home WiFi as I don’t have split SSIDs.

    I don’t have a lot of Bluetooth devices at home, but I do have a Bluetooth ODB2 adapter I can connect to, so I’ll test that.

    Streaming and video playback did work, for a short period of time mind you, in the v1 devices, and as there wasn’t any improvements on cooling in the new version, I’d assume the v1.5 will die after the same time period.

    There looks to be a new firmware on it, so I can check to see what happens with the major streaming services, other then Netflix of course, if there is video along with the audio.

    jerwam
    Participant
    Post count: 62
    in reply to: test image #3307

    Well, firstly God knows why I can’t edit the post – but at least the image is working. Secondly, I can’t delete the post either, but more importantly… as you can see from the image the v1.5 device has a working GPS, in the real world, in a car, and it updates while driving!

    I did a quick test while driving around my neighborhood, and Google Maps worked as expected! Even with a couple of wrong turns thrown in to make sure it was able to reroute me accordingly, and it worked, this is the device I paid for. No need to connect the unit to my phone to the GPS Mirror app, it worked out of the box.

    I will say that it was hot to the touch when I unplugged it, but it didn’t turn off like some of the v1 devices were doing during video playback. I haven’t tested any video playback/streaming as that wasn’t the reason I purchased the device, but more importantly with my 2013 Ford Focus not having AC at the moment, I am not about to sit in 32C heat to find out what happens.

    I’ll do some more testing on the unit when my Wife gets home with our Prius, mainly testing a longer drive to see if the heat does cause it to shut down at all. Do let me know what else you’d like me to test and I’ll make sure to get it done.

    Cheers

    jerwam
    Participant
    Post count: 62

    I’d be willing as well. Eagerly waiting to see the improvements on the GPS.

    Email sent.

Viewing 15 posts - 1 through 15 (of 56 total)