how is the bluetooth holding up? Is it auto pairing everytime you start the car? I have a monoprice bt receiver that was powered by usb, but it wouldn't connect automatically often enough.
finally got around to installing a plate to cover up all the holes in the dash from the previous carputer project.
i used 2 coats of fine textured paint, then sanded it lightly to knock the texture down a bit, then did 2 coats of satin black. it came out looking very close to the factory finish on the other black plastic areas. i went with the black because i figured if i tired to use tan but didn't get it exactly to match the dash color then it would look bad.
Last edited by theksmith; 05-14-2013 at 02:57 PM.
power is connected (which is the jeep starting), so far it always re-connects immediately in that situation all by itself.
a few times the tablet has locked up and i've had to restart it (not sure if it's an app or the ROM or what). when doing a cold start something seems to happen a little out of order and even though bluetooth comes on and it sees the logitech receiver, i usually have to manually click on it in the list of devices to get it to re-connect. i've never had to go through the whole pairing procedure again though. i probably just need to really step through my Tasker scripts and see if i'm doing something silly in this situation.
finally got my project on the go as we have a major trip ahead and am cleaning up the cruiser.. I eventually replaced the old non-functional headunit with a Sony MEX-BT4100P - this allows pairing with both my phone for handsfree and the tablet for media so I don't need to mess around further with that - seems like a bit of a waste, but it works a treat.
I wanted to ask if you ever got a 2.5" usb harddrive to work on the USB hub - my tablet is simply ignoring it completely and was wondering if I should persevere or forget about it..
i flashed a new rom and kernel recently, so i might investigate this further now...
it's been a while since i updated this thread but everything has been working great except for my steering wheel button interface. the app would intermittently stay running when i shut the jeep off and then not work again till a reboot. this happened maybe 3 out of 10 times that i used the tablet and so it was hard to troubleshoot. after flashing multiple ROMs, kernels, and even refactoring my app to use the newest version of usb-serial-for-android driver - it turned out to be a damn hardware issue! anyway, it's fixed now and i'm ecstatic that the final little bug is worked out (at least till i get a wild hair and completely re-do a bunch of stuff !)
after trying multiple 4.1 and 4.2 based ROMs, i ended up on the last nightly build of CyanogenMod 10.1 for Stingray (the 9/8/2013), then flashed the ElementalX-Xoom-v1.2 kernel. UPDATE - just saw there's a new CM nightly from just last night, i'll wait to see if they ever finish a "stable" release since i'm not having any issues though.
i found the Team EOS 3 & 4 releases to be very stable too, but i missed some of the CM features. if you wanted to stay on a 4.1 based rom, i'd go with EOS 3 over CM 10 though, it doesn't have the issues with the system partition.
side note - i was having a really hard time dealing with the fact that there's no Tablet UI anymore in 4.2, it just doesn't make sense to only have the Phablet UI, especially in landscape mode - total waste of space. i couldn't get the Auto-Patcher Utility to apply the TabletUI mod to any of the recent CM 10.1 builds though anyway, i eventually just got used to the stupid top bar.
i recreated all of my tasker automation. it came out much cleaner and simpler this time. the only issue i found was that the media button pause task no longer worked correctly in Android 4.2. music apps would pause, but then randomly start playing again later. doing a shell command "input keyevent 85" works reliably though (requires root).
now using Nova Launcher instead of Apex. not quite as many features, but it's more responsive. also when using Apex i had problems with the Pandora widget no longer responding to touches occasionally.
i switched to this ftp server app for remotely updating the tablet: https://play.google.com/store/apps/d...utey.FTPServer
previously i used the one built into ES File Explorer, but found it would time out on large files.
i'm also evaluating a newer mapping app for offroad use, Alpine Quest. I'm liking it better than Backcountry Navigator so far, much faster and without some limitations that BCN has. it isn't as feature rich as Orux Maps yet, but it's handling of offline maps is superior and it's still a young product so hopefully the dev keeps improving it.
i think i'm still using all the other apps that i previously mentioned in this thread. oh, one thing i noticed is that the developer removed the "Metrostation" app from the play store. glad i had it backed up as i'm still using icons from it for my desktop.
Latest home screen shots
notice in the above one, i've changed my manual "mode" selection to just using a desktop folder with tasker shortcuts in it instead of doing a custom tasker "scene".
Last edited by theksmith; 09-16-2013 at 07:46 PM.
someone on another forum asked for details about what the hardware issue was with the steering wheel interface. my response:
i don't actually know for sure exactly why it was happening, but i have a fuzzy picture of the problem...
quick background - when i setup everything, i used a powered USB hub and configured things so it was only powered when the Jeep was on. my only USB device so far, the OBDII interface, was also set to only be powered when the Jeep was on. however, since the hub was always attached to the tablet (by virtue of it being in the cradle), the tablet would have ended up powering the hub even with the Jeep off. this was undesirable for many reasons, mainly tablet battery drain. therefore, i severed the +5V (red) wire on the tablet OTG cable so that the tablet couldn't provide power to the hub.
i realized recently that a USB device can be considered "connected" with only the 2 data lines intact (i.e. for self powered accessories), so i probably should have used a multi-contact relay to completely disconnect the OTG cable from the hub. i believe the problem was in the timing of everything shutting down, depending on whether the OBDII interface was in the middle of sending data and then maybe even whether the hub or it shut down first (talking micro seconds here).
i happened to have a another very fancy USB hub designed for carputers laying around, the Carnetix P5USB. besides featuring a true complete disconnect/shut-down that could be triggered by ignition, it also isolates each port and prevents any back-bleed of +5V from an accessory. replacing my previous dumb hub with this one solved the problem. since this hub has so many features, i can't be certain exactly which one was the actual fix.
released a newer version of my steering wheel button interface app for Android. mostly minor fixes, code cleanup, improved documentation, etc.
source code here: https://github.com/theksmith/Steering-Wheel-Interface
Last edited by theksmith; 09-18-2013 at 08:53 AM.
Excellent I'll have to check it out. About ready to install my new nexus 7. The biggest hold up for me was usb audio support, hopefully that will be available by the time I start my install.
"You're just about as useless as JPEGs to Helen Keller" - Wierd Al