Database Info

Android In-Vehicle Infotainment

So I've had a project for the last few months getting Android running as an infotainment system. Here is a demo i thought i'd share with you guys..
http://www.youtube.com/watch?v=fNcDq9S8n3I
Basic features:
Android 2.1 (looking to update to GB)
7inch touch-screen (800x480)
3G modem
GPS
Reverse camera (backup camera to see what's behind you)
USB port
would love to hear some criticism or anything regarding the device.. its not perfect, its got a few bugs and glitches.. but is sort of ready for everyday use but is missing a few components to make it 'official' android device (wifi, bluetooth etc).. but i'm just wondering if anyone is interested in something like this? Is this worth developing further on?
This thing runs on Cortex a8 omap3530 board and is based off 0xdroid build.
apologies if im in the wrong forum

Wow dude, thats really cool! I'd love one of these for my car. If you could get Honeycomb on that bad boy it'd be sweet! Just wondering, how do you plan on setting up a rear view camera? Just connect a camera at the back of the car to the tablet itself, then run the Camera app? Seems like the simplest way to me..

Haha cheers love to see the honeycomb source once its out then we'll talk although I'd imagine i'd need better hardware...
currently camera is interfaced by usb (has a usb hub) so i got a cable running under the carpet through the boot then camera is mounted on the bumper. yup camera is called by any camera calling intent.. so any app can use it.
I want to get some proximity sensors (like parking sensors) and write a proper reverse cam app to complement it. But we'll see...

Very cool!
I've been wanting to do this for a while, but I was going to use MeeGo or maybe Moblin since I don't have the programming skills (or Android knowledge for that matter) to build my own computer around Android. I dig what you got so far though.
My suggestion for the reverse camera is one of two things, because it would bug me to have to find and open the camera app every time I needed to back up.
Keep your touchscreen (what model are you using BTW?) and use a bluetooth or wi-fi relay (I know they make 'em, but they are $$$) to provide an input from +12V signal from your reverse light wire to automatically open the camera app, then close the app. Of course, you'd have to program for that.
Or
Have you considered this touch screen? Lilliput 7" touch screen with auto-reverse input. (Needs a RCA camera though)
http://store.mp3car.com/Lilliput_629GL_70NP_C_T_7_VGA_Touchscreen_w_Aut_p/MON-016-0002.htm
This is the one I plan on using since it switches automatically to the camera input whenever you are in reverse. Once you go back to any other gear, the OS input shows up again.
Just a thought to make life a little more convenient (although you already bought your parts so you may be stuck.)

chjade84 said:
Very cool!
I've been wanting to do this for a while, but I was going to use MeeGo or maybe Moblin since I don't have the programming skills (or Android knowledge for that matter) to build my own computer around Android. I dig what you got so far though.
Click to expand...
Click to collapse
Thanks a lot! It needs a lot of time and dedication but it's a real good learning curve. I had to learn a lot of things on the way.. especially c/c++ I wasn't great at but had decent skills with higher level programming.
If you are planning to work with MeeGo its a little fussy with the hardware requirements.. Correct me if i'm wrong, but I think you need an Intel Atom processor. These are a little pricey if you're after an evaluation/hackable kit! But I'd imagine it'll be easier to program as it's a lot more closey coupled with linux.
chjade84 said:
My suggestion for the reverse camera is one of two things, because it would bug me to have to find and open the camera app every time I needed to back up.
Keep your touchscreen (what model are you using BTW?) and use a bluetooth or wi-fi relay (I know they make 'em, but they are $$$) to provide an input from +12V signal from your reverse light wire to automatically open the camera app, then close the app. Of course, you'd have to program for that.
Click to expand...
Click to collapse
I just had a look at those relays, sounds like its something I really need! Is this how the standard backup cameras work? That was something I was confused about.. I wasn't sure how to detect if i'm on reverse.. especially with the parts I already had. I'd imagine once you implement it you just need a service running in the background to listen for the relay.
The touchscreen is a TFT resistive 4wire touch-screen. It's not something I want to keep as I really want capacitive multi-touch.. But this fits perfectly with the board and was easier to deal with
chjade84 said:
Or
Have you considered this touch screen? Lilliput 7" touch screen with auto-reverse input. (Needs a RCA camera though)
http://store.mp3car.com/Lilliput_629GL_70NP_C_T_7_VGA_Touchscreen_w_Aut_p/MON-016-0002.htm
This is the one I plan on using since it switches automatically to the camera input whenever you are in reverse. Once you go back to any other gear, the OS input shows up again.
Just a thought to make life a little more convenient (although you already bought your parts so you may be stuck.)
Click to expand...
Click to collapse
Nice find! I wish I saw that earlier .. Quite pricey but would make life so much easierrrrr!
Cheers for the feedback! Best of luck for your project!

tknz said:
I just had a look at those relays, sounds like its something I really need! Is this how the standard backup cameras work? That was something I was confused about.. I wasn't sure how to detect if i'm on reverse.. especially with the parts I already had. I'd imagine once you implement it you just need a service running in the background to listen for the relay.
Click to expand...
Click to collapse
I think most factory backup cameras use two inputs and switch between them. I don't have a lot of experience with them though.

chjade84 said:
I think most factory backup cameras use two inputs and switch between them. I don't have a lot of experience with them though.
Click to expand...
Click to collapse
Not sure what you mean exactly. I'll try the relays because it at-least gives me a standard interface to work with (bluetooth or wifi) so there isn't any work you have to deal with on the hardware abstraction.. Although it would probably be better designed if I had some sort of voltage input coming when the vehicle on reverse (the reverse light as mentioned). But I don't really have the electrical expertise to make it happen lol.

tknz said:
Not sure what you mean exactly. I'll try the relays because it at-least gives me a standard interface to work with (bluetooth or wifi) so there isn't any work you have to deal with on the hardware abstraction.. Although it would probably be better designed if I had some sort of voltage input coming when the vehicle on reverse (the reverse light as mentioned). But I don't really have the electrical expertise to make it happen lol.
Click to expand...
Click to collapse
Well essentially what I was thinking was you'd have the bluetooth relay hooked up to your reverse light wire. This should allow your computer to monitor whether or not your car was in reverse. Relays are pretty simple - one input switches on/off another, usually one of a much higher or lower voltage. So in essence, it's a switch activated by voltage. (There used to be an electromagnet inside that physically moves a piece of metal to make a connection when a voltage is applied - now it's all transistors and whatnot.)
So, if you are in reverse and your reverse lights are getting power, the bluetooth relay should sense that and signal the computer (through a serial command it seems) which in turn could tell a background service to open the camera app. Once the voltage from the reverse light wire is lost, the relay should again tell the computer that you aren't in reverse anymore and the background service would close the camera app and re-open whatever app you were in.
*I should note this is all "in theory"... I don't know exactly how those wireless relays work/communicate and I don't know Android programming at all.

Thanks for the feedback. I was thinking what about using the GPIOs on the board and attach that to the reverse light? would that be possible? and using some resistors on the way to limit the voltages so i don't fry the board.. but we just need to detect some voltage input...
Not sure, will look into it. Right now, taking a pause on the development.. Got a lot of work to take care of but I can't wait to get back into it. I really want to port this to gingerbread.

tknz said:
Thanks for the feedback. I was thinking what about using the GPIOs on the board and attach that to the reverse light? would that be possible? and using some resistors on the way to limit the voltages so i don't fry the board.. but we just need to detect some voltage input...
Not sure, will look into it. Right now, taking a pause on the development.. Got a lot of work to take care of but I can't wait to get back into it. I really want to port this to gingerbread.
Click to expand...
Click to collapse
You could possibly do that, a real cheap voltage regulator would probably be better though. You could also use a cheap relay if the correct voltage is already somewhere on the car. Again, I'm not too sure how those bluetooth relays work, but it sounds like you are on the right track.

Great Job!
I was thinking of doing something similar myself.
I am looking at going with one of the tablets as it is just seems easier? I only really need internet, google maps(GPS) and wifi tethering. I would imagine you are running stereo sound from a 3.5mm? I would still have a seperate head unit to control volume and handle all the regular functions as well as inputs from a 3.5 to RCA cable.
How are you running sound off that setup? Are you running a head unit still?

The sound is running off a small amplifier. then RCA to 3.5mm.
Haven't had the chance to play around with the wifi tether as right now i don't have a wifi card.. It would make sense to have wifi tethering or just wifi reciever and use a phone to tether 3g to the system. Avoids having separate data plans.

Can we get a copy of your "AIVI Car Home" for our own DIY projects?

I don't mind releasing the source for it. Its just right now its a bit messy and quite a few things are hardcoded.

tknz said:
So I've had a project for the last few months getting Android running as an infotainment system. Here is a demo i thought i'd share with you guys..
Click to expand...
Click to collapse
Nice project. I gutted a Clarion Mind last year to do pretty much the same thing but am looking to upgrade. You said the software needs work but it's a real good start. Would you mind sharing your hardware list with us?

Nice work!

Something I was also interested in seeing is having vehicle manufacturer recommended service intervals and such available as reminders from your in car system or phone or both.

Stu_Gotti said:
Something I was also interested in seeing is having vehicle manufacturer recommended service intervals and such available as reminders from your in car system or phone or both.
Click to expand...
Click to collapse
You could use 'aCar' which, if you are unfamiliar, you enter the make, model, mileage and all the pertinent service requirements. Battery every 3 years or 50,000 miles, coolant every year or 15,000 miles, oil every 6 months or 3,000 miles, etc. Then, every time you get gas you enter the current mileage as well as gallons/liters of fuel and the price. From that information you not only get your MPG but it will also trigger reminders to do the necessary maintenance at the correct intervals when they come up. You can do this for multiple cars as well. It's a very good program.
On a related note to this thread, I started my own 'carputer' project using an Archos 70 Internet Tablet and an unused articulating wall mount for TVs. It's still a work in progress as well since I don't have all the parts yet but will do everything I wanted (eventually... lol) except the rear facing camera. The video is obviously just of the media player.
I shot this late last night to show a friend. He wanted to know why someone would want a tablet/computer in their car, lol. Sorry about it being so dark.

Dude
I am keen as mustard on one of these beauties, I was considering running xp MCE but the android option would be much nicer..
Love ya work.

tknz said:
I don't mind releasing the source for it. Its just right now its a bit messy and quite a few things are hardcoded.
Click to expand...
Click to collapse
Please do. Would love to play with it. No matter how clean the code is it's just gonna get better...
thanks for showing it..

[Q] TV out on ICS

Hi, so I've been ICS for a while now and I'm currently running Virtuous Infinity 1.35beta. A few days ago I stumbled upon my cable that I used to use when I was on Gingerbread for connecting the MT4GS to the tv. It's a 4 pole jack with a red, white and yellow on the other end. Ever since I came over to ICS, I haven't had much time to play with this, but when I wanted to watch a movie on the tv off my mt4gs, it did not work. The phone tells me something along the lines of "hdmi connected", but the screen on the tv just turns blue and does not show anything. The movie plays on the mt4gs without a problem. I'm posting this because all of the threads I found about similar issues are from 2011 or early 2012, i.e. long before we got the ICS.
Does anyone have any idea of how to get this to work properly? Or is reverting back to Gingerbread the only option of getting this to work?
I bought this phone to last me a while and I'd hate to lose a useful function like this, where you can always essentially have a movie player in your pocket.
Thank you for even the slightest input you can give me on this because I haven't been able to find anything on this issue on xda or google.

lubotron said:
Hi, so I've been ICS [...] A few days ago I stumbled upon my cable that I used to use when I was on Gingerbread for connecting the MT4GS to the tv. It's a 4 pole jack with a red, white and yellow on the other end. [...] The phone tells me something along the lines of "hdmi connected", but the screen on the tv just turns blue and does not show anything.
Click to expand...
Click to collapse
I saw the title to this thread in the forum list and it prompted me to find my cable. I'm going to have a few days coming up here where it will come in quite handy and I want to make sure the ROM I'm using is fully functional for my purposes. REALLY ticks me off how this phone seemed to be built only for Sense 3 Gingerbread. I think I'm going to quit supporting HTC over this BS.
So I finally find an ICS ROM that doesn't seem like it's crippled all to hell, and I saw this thread, and decided to try it. So far everything else I've needed seems to work, and I just went 12 hours with only 5% drop in battery (of course not touching the phone -- once I do it's like I lose a percent a minute) so it seems like a pretty decent ROM. But then I plug it into the tv, and just like you, I got "HDMI Connected" in the notebar, a blue screen on the tv (with black interleaved horizontal lines), and no other output. Also, there's no "TV Out" app or any kind of config that I can find.
I'm going to go hunting and if I catch anything I'll bring it back here...

http://forum.xda-developers.com/showthread.php?t=1484165
that's probably your best bet. just a warning, i'm pretty sure it drains battery quickly (which i guess kind of makes sense cuz of the name "brute force"). not sure if this is exactly what you're looking for, but it's a start!

anitgandhi said:
http://forum.xda-developers.com/showthread.php?t=1484165
that's probably your best bet. just a warning, i'm pretty sure it drains battery quickly (which i guess kind of makes sense cuz of the name "brute force"). not sure if this is exactly what you're looking for, but it's a start!
Click to expand...
Click to collapse
Anybody knows if tbalden released the source of this tvoutd binary? Would really love to work on this one if I could get hold of the source.

Riyal said:
Anybody knows if tbalden released the source of this tvoutd binary? Would really love to work on this one if I could get hold of the source.
Click to expand...
Click to collapse
I don't think he posted/released the source for the tv out app. Try sending him a PM. I'd be interested in helping you with this, if tv out via micro usb is even doable.

rumi409 said:
I don't think he posted/released the source for the tv out app. Try sending him a PM. I'd be interested in helping you with this, if tv out via micro usb is even doable.
Click to expand...
Click to collapse
Don't confuse tv-out (via 3.5mm 4-conductor phone plug) with MHL (via micro-USB connector/adapter) though...
...and I read in another xda thread that this phone may have the same
MHL chip that another phone had... Was it the sensation?
--
Sent from my Bulletproof HTC Swiss Army Doubleshot

All the guys who have examined it and worked hard on the subject have stated that it simply is not built in such a way as to do MHL. Blue IIRC was the guy who made the definitive statement.
Hastily spouted for your befuddlement

I tried dissecting the binary to extract as much information as I can have and I noticed that this daemon is hacking up the route of the hdmi to the headset passage and into the usb to the TV. I'm not really good into these technology as I am not even using HDMI lol! So unless there's a source code I can't continue development on this as I don't understand the process of this bruteforce hack.

Not sure who to contact about dock line out redirection in CM10

So one feature not many people realize the Samsung Galaxy S3 has is the ability to redirect the line output through a dock. This is particularly helpful in a car where you can have it actually output straight to the stereo system when you plug it into a dock, but even in a home environment it can be handy if you have a dock with speakers built in or just leave something plugged into a dock for convenience. However, it seems in CyanogenMod 10 monthly at least it doesn't work. When I clicked the "request device support" button (thinking he probably wouldn't even touch CM10 given that it's still not really "officially supporting" the SGS3 yet anyway, I did get this response:
Please have the ROM dev supporting your model verify the correct mapping exists between the ROM audio device and the kernel audio path (commonly set in libaudio).
Example: DEVICE_OUT_ANLG_DOCK_HEADSET in ROM should map to the path PLAYBACK_EXTRA_DOCK in the kernel.
Regards,
Dan
Click to expand...
Click to collapse
So if I go by this it sounds like it's mostly just a matter of a configuration in the audio libraries being used and I just need to let someone know.
I know this isn't important by any means, but it does seem like something that should probably still go in there just whenever they could get around to it. It can be very convenient at times IMO.

I believe all the framework is there.. we are just waiting on http://review.cyanogenmod.org/#/c/25274/ to be merged.
Nazo said:
So one feature not many people realize the Samsung Galaxy S3 has is the ability to redirect the line output through a dock. This is particularly helpful in a car where you can have it actually output straight to the stereo system when you plug it into a dock, but even in a home environment it can be handy if you have a dock with speakers built in or just leave something plugged into a dock for convenience. However, it seems in CyanogenMod 10 monthly at least it doesn't work. When I clicked the "request device support" button (thinking he probably wouldn't even touch CM10 given that it's still not really "officially supporting" the SGS3 yet anyway, I did get this response:
So if I go by this it sounds like it's mostly just a matter of a configuration in the audio libraries being used and I just need to let someone know.
I know this isn't important by any means, but it does seem like something that should probably still go in there just whenever they could get around to it. It can be very convenient at times IMO.
Click to expand...
Click to collapse

mastamoon said:
I believe all the framework is there.. we are just waiting on http://review.cyanogenmod.org/#/c/25274/ to be merged.
Click to expand...
Click to collapse
Ah, this is good to hear. It's obviously no high priority, so it will go in when it goes in, but I was worried I'd have to contact all sorts of people to bring it up as it seems like something they wouldn't have even thought of.
Thanks for the info.

I want this also, believe me. I just bought 5 of the Infuse 4G docks that ATT had on sale for 5 dollars. 2 desk docks and 3 car docks.
Nazo said:
Ah, this is good to hear. It's obviously no high priority, so it will go in when it goes in, but I was worried I'd have to contact all sorts of people to bring it up as it seems like something they wouldn't have even thought of.
Thanks for the info.
Click to expand...
Click to collapse

I'm cheating. I ripped apart a desk dock that was being clearanced out by a seller on Amazon for the Galaxy S2 I think it was, and adapted it to be my car dock. The USB connector is on a small cable already, so the cable just sticks out and the rest of the electronics are housed in a micro-sized Altoids tin (one of those little ones you can buy for $1 or so.) This way I can just plug it in and it's compatible with my Otterbox, so this method can be convenient for anyone who wants a "dock" that's compatible with skins and cases at the catch that the cable must be manually plugged in after dropping it into a generic dock. Super-cheap too since so many of the older ones are being clearanced out with the SGS3 now out. The only catch being that, of course, some work is required and of course anything remotely resembling a warranty on the dock is utterly wiped out, lol.
Along with a dock control app that is set to automatically change settings like Bluetooth and to start my audio player, it's super convenient to just drop the phone into the generic dock in my car, plug that cable in, and I'm ready to go. I was using the line output redirector tool along with the stock firmware, but in the end I'd rather CyanogenMod and something minor like no line output redirecting (yet!) was no deterrent...

mastamoon said:
I believe all the framework is there.. we are just waiting on http://review.cyanogenmod.org/#/c/25274/ to be merged.
Click to expand...
Click to collapse
I looked at that link but can't figure out how the CM projects work. Is this change for Verizon GS3 only or is going to be included for all carriers? Also, the status of the change is merged. How can I see which nightly this went into?

I could be wrong, but I'm inclined to say that something like this would be at a different level than anything carrier-specific as it's really just a hardware-specific level and thus should be the same across all carriers. However, if it helps any, I can say that I'm using d2vzw (aka Verizon.)
Also, the status of the change is merged. How can I see which nightly this went into?
Click to expand...
Click to collapse
Ah, I didn't notice that. I just checked on mine and it's in the stable 10.0 which I switched to the other day. I don't know what nightly it might have first made it into, but in other words, it's there now. I'm using the "Galaxy Dock Sound Redirector" app personally.
EDIT: Woops! Correction. I was using that program from before because the original firmware required it to redirect the sound. However, it looks like there is a setting in the advanced section under sound. I haven't tested to see if it works as fully for me (it's not helping that I use a dock originally made to be a "desk" dock in my car, so a lot of things react differently) but likely that app is only necessary with the stock firmware.
EDIT2: Had time to test it now. CM10 stable's dock output works perfectly entirely on its own. I don't need a third party app or anything. It's just in kind of an unusual location (IMO it might be better if it were in the sound section.)

So I recently updated to the 10.1 now that they have a monthly available (basically it was suggested to me that monthlies could be considered more "stable" and reliable than, say, nightlies if any CyanogenMod could really be called stable, lol) and much to my chagrin it seems like the dock audio no longer works with this one even though that patch was supposedly accepted for 10.0? (Surely they wouldn't remove it?) Is something just set wrong, or has dock audio support on the SGS3 actually disappeared after they went to all the trouble to add it?
It's a sad day to see something take a step backwards like this. I can only hope it will be resolved later, but who knows?

[Q] Hardware Radio Issues with Nexus 5

I got a Nexus 5 off a friend for a decent price because he dropped it and bent it up a bit. After giving it a quick look, the only thing that seemed damaged was the black little coax wire that connects the main board to the board on the bottom (Assuming it goes to the antenna), The end simply got bent off. This was an easy fix, replace the cable no worries. The real problem is when I went to go test the phone after I fixed the cable, it doesn't get any cellular signal (Wifi/BT still works), draws a crazy amount of power and the 'Qualcomm WTR1605L' chip specifically gets extremely hot, to the point of overheating in like 30 mins. Rather than tossing a bunch of money into replacement components (or getting another nexus 5 with a bad screen or something) I'd prefer to narrow down the problem to one specific component. This leads to my question:
Does anybody have any ideas to how I can further troubleshoot and diagnose this problem, or knows what the problem exactly is?
I have tried a few things, like if I flash the LG G2 radio (A trick I learned I could do with my Nexus 4/LGOG, after backing up my EFS just in case), Wifi and Bluetooth still work while Cellular, GPS and most of the other sensors do not. This stops the big power draw and overheating issue, but doesn't really do anything to further identify the problem component. I noticed that the modem image could be mounted as vfat and you can mess around with the various parts of the image. I don't know which files do what, so I have thus far left it alone.
I know this seems like an odd question to ask here, half the time I see responses like "Send it into Google/LG and have them fix it for you" but that isn't really applicable in my situation
Also, I know that my SIM is good, it works in my Nexus 4, I know that my ROM isn't a issue, because I have multirom installed and tried many different roms. The Radio image shouldn't be an issue because I had updated the phone from 4.4 to 4.4.4/L Preview since I got it (Using the google images and flashall script). IMEI/Whatever the ESN equivalent shouldn't be bad, my friend had been using it before he dropped it.
Thanks in advanced for any ideas, and sorry for the long and comprehensive almost to a fault thread.

dtalley11 said:
After giving it a quick look, the only thing that seemed damaged was the black little coax wire that connects the main board to the board on the bottom (Assuming it goes to the antenna), The end simply got bent off.
Click to expand...
Click to collapse
Dropping a phone can sometimes cause invisible damage (like BGA solder joints failing). Visual inspection can only tell you so much.
dtalley11 said:
This was an easy fix, replace the cable no worries. The real problem is when I went to go test the phone after I fixed the cable, it doesn't get any cellular signal (Wifi/BT still works), draws a crazy amount of power and the 'Qualcomm WTR1605L' chip specifically gets extremely hot, to the point of overheating in like 30 mins.
Click to expand...
Click to collapse
I used to build small electronic projects when I was a kid. When something overheated like that, 90% of the time it was a short or a the wrong value of component. It's possible the drop caused the antenna connector to short out. Try disconnecting the antenna cable and try again with the stock radio firmware and see if the radio continues to overheat.
(I'm not sure how flashing the radio would prevent overheating, unless the original firmware simply turned up the transmit power in an effort to contact the tower, but that's my first guess and should an easy thing to eliminate).

ScottyPcGuy_03 said:
I used to build small electronic projects when I was a kid. When something overheated like that, 90% of the time it was a short or a the wrong value of component. It's possible the drop caused the antenna connector to short out. Try disconnecting the antenna cable and try again with the stock radio firmware and see if the radio continues to overheat.
Click to expand...
Click to collapse
Thanks for replying! When I get home I will give it a shot and see if it still overheats, then update this with my findings.

If it is overheating then it must hardware issue. Worst case is that the PBC board has a crack somewhere because of the bent. Grab the service manual from the general forum and start mesuring the components to find out where is the problem.

bitdomo said:
If it is overheating then it must hardware issue. Worst case is that the PBC board has a crack somewhere because of the bent. Grab the service manual from the general forum and start mesuring the components to find out where is the problem.
Click to expand...
Click to collapse
Ah, thanks. Something like that should be a sticky. For future reference/making sure we're on the same page, I found the thread here: http://forum.xda-developers.com/google-nexus-5/general/service-manual-d821-t2791303

dtalley11 said:
Ah, thanks. Something like that should be a sticky. For future reference/making sure we're on the same page, I found the thread here: http://forum.xda-developers.com/google-nexus-5/general/service-manual-d821-t2791303
Click to expand...
Click to collapse
Yes that is it.

ScottyPcGuy_03 said:
I used to build small electronic projects when I was a kid. When something overheated like that, 90% of the time it was a short or a the wrong value of component. It's possible the drop caused the antenna connector to short out. Try disconnecting the antenna cable and try again with the stock radio firmware and see if the radio continues to overheat.
(I'm not sure how flashing the radio would prevent overheating, unless the original firmware simply turned up the transmit power in an effort to contact the tower, but that's my first guess and should an easy thing to eliminate).
Click to expand...
Click to collapse
It seems to overheat with our without the antenna cables on the stock radio. I noticed that it still gets warmer than it should with the G2 radio, it just takes a lot longer.
That service manual is really comprehensive but unfortunately, it is going to take me some time to actually get to looking it over closely.

Just had to share this experience....

Well I have been a owner of a LG Nexus 5 for the past (almost) 2 years now, in fact I am coming to the end of my contract very soon and will be able to either goto another company or get a new phone.
Anyways, sometime ago I experienced a problem with my microphone and external speakers not working, or at at least some of the time... After a bit of research online I found out my problem was related to a connection inside the phone that connected the bottom assembly to the main board at the top of the phone. It required me to remove the back panel and a few screws to remove the plastic cover, but the poster suggested putting some tape on top of that connection to hold it down more firmly to the socket it connected too. So I did this. I put some black tap (electrical tape cut to fit.) on top and then assembled the phone again. Viola, It worked!
Well, a short time after I decided that I wanted to update my phone from stock kitkat (4.4.4). Always been curious about custom ROMs and gave Cyanogenmod a try. Not only that I got bold and tried the nightly releases of the new marshmellow update. After some time I started experiencing things not working, like the camera, and a lot of freezing, hang ups and random reboots (not so much the reboots as the constant freezing). Often I couldn't get anything on the screen or the phone to respond from a locked state and when I did, often the phone would lag so much, that doing anything would take a long time and proved to be impossible.
I started thinking it was the nightly releases as the source of my problem and just kind of shrugged it off and figured "they will eventually fix the problem". I kept this thinking for quite some time. But it occurred too me one day that something else was causing the issue I was facing for the simple fact that the lag started showing up in the recovery mode (also custom) and a lot of times would continue to show up after I rebooted my phone. Hence, would rule out any 'software' issues I was facing.
I began to think that my problem was hardware. Maybe it was just time for a new phone. But still months away from the end of my contract, this meant I would have to pay off the 'problematic' phone first before getting a new one. I really didn't like that idea. So while looking into this problem, in a last ditch effort, I opened my phone again. Dunno why but I also decided to get rid of the tap on the connection I tried to fix before... I popped off the connection there and had a look at it. It didn't seem damaged in any way nor did the socket. Strange as it was I put that connect back in the socket and put the cover plate back on making sure not to torque the screws and assembled everything back up....
Now the mic and ext speakers work just fine and the phone is working like I just opened the box and took it out for the first time. And I have not once seen any problems... I understand what's happening here... still just wanted to share that for it was definitely weird or what?

https://drive.google.com/open?id=0B0pUNVcVRCJ7MThMc0NHLUNkSEU
Sorry about the link, only way I can upload an image.
Just so there is no confusion... an image of the effected area, inside the phone. The arrow points to the connector and more importantly the area of the connector that seems damaged. If I press lightly where the arrow is pointing on this image, the assemable at the bottom (speaker/mic) will work, indicating a loose connection. Although after visual inspection, I cannot see any damage to connector or the socket. I suppose the only way to really "fix" the issue is to order a new part. As stated previously, already tried tape on the socket to help hold it down, but that seem to cause just as many issues with the phone performance. Any other suggestions?

When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357

Does anyone else have issues with there ext. speaker and mic not working?
An update on the phone;
back to square one. My ext speaker and mic will not work. And that socket has something to do with the LCD connection on the screen as it will black out if just the right area on the back of the phone is pressed. Only way to revive the phone is to long-press the power button for a reboot. Then will come up fine but speaker and mic still do not work.

audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
Wow, that sounds pretty low level tactics of LG... just shameful really, but not hard to believe these days...
Quite honestly, I am just going to replace the phone. Think I got a pretty good run out of it and think its pretty well time for an upgrade. Anyway, for the reason I got the phone, it wont matter the speaker and mic don't work. Just going to use it for development and it will be a good test device.

Oh an this post is related to this thread so I thought I would link it for it may help someone else facing similar problems....
https://forum.cyanogenmod.org/topic/125227-nightly-cm13-releases-make-my-nexus-5-very-slow/

I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.

audit13 said:
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
Click to expand...
Click to collapse
Good idea, except the iphone is the most popular phone around here ... find it pretty hard to find one, been looking. But thanks.

I have seen quite a few busted n5 phones in Toronto. I have managed to get working phones with a smashed screen for as little as $30 which is rare for Toronto. Average I pay is $40 to $50. For this price, I either use the phone for parts in several phones or I get third part screen from Aliexpress for around $40 CAD.

I just want to update this as well...
I am fairly certain (now thinking about causes) its not really a design flaw, but more so because I frequently sat on my phone when it was in my back pocket...

audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
It was not me but I had that same experience. Replaced with a cheap oem and it didn't charge after that.
I found out why. The charger usb socket was not connected to anything ! Unbelievable! It lacked the black plastic backing for that part of the cable to connect to.