Related
First off I'm not sure if this is the right forum for this and I also searched for the past few days and have had no luck finding anything much on this. Most stuff I come accross is talking about the phone having a built in fm transmitter that doesn't work - blah blah blah. So here goes, I'm now on Paul's Froyo ROM and for the first time decided to try using the phone for playing music in my car thru a wired fm transmitter and it was not good. I now have three fm transmitters (2 I bought and the final one my brother gave me his that he used to use in his car with no problems) all give me the same results which is it seems okay playing through parts of songs that don't have much bass but once bass starts to hit it gets all awful stattic sounding and the Stereo (ST) indicator on my radio blinks so somehow the sound quality goes all bad. I've narrowed it down to obviously being something with the phone somehow cause I've tried with iPhones and another MP3 player and they (FM transmitters) work perfectly. I've also tried it with IntersectRaven's and CM's kernels for Froyo to see if the kernels might make a difference and no luck. So my question is, is this a known issue with the N1 or is this an issue with Froyo and isn't the case with say CM 5.0.7.1, anyone with experience can shed some light? Was thinking to go back to CM but after seeing all the threads of the issues in doing so decided not to but if this is not the case with other ROMs then it would make me switch back until a official Cyanogenized Froyo is out. If this is the wrong forum then my apologies and Dev's plz move to correct forum.
Update: I've messed with it some more and have been able to get it to play fine with Pershoots kernel but I have to turn down the media volume to approximately 70%. So it seems to me that with the media volume up all the way it must be drawing too much power or something from the headphone jack to make the output all distorted. I haven't tried with IntersectRaven's kernel to say if I get the same result since I'm just happy the darn thing works now. I'll also do a post in the Develoment forum linking to this in case anyone there may want to investigate this issue.
Sounds to me like every experience I've ever had with every FM transmitter. They just don't transmit loudness or bass well. I don't think it's the phone, I think its the FM Transmitter technology.
edit: could just be the volume boost or something on the specific kernel (not even sure if the kernel's you are talking about have a volume boost) but that may increase the max volume out and cause the problem.
derfasaurus said:
Sounds to me like every experience I've ever had with every FM transmitter. They just don't transmit loudness or bass well. I don't think it's the phone, I think its the FM Transmitter technology.
edit: could just be the volume boost or something on the specific kernel (not even sure if the kernel's you are talking about have a volume boost) but that may increase the max volume out and cause the problem.
Click to expand...
Click to collapse
yes exactly, try a vanilla kernel and see how that plays out... I am curious of your findings...
Kman Gymrat said:
First off I'm not sure if this is the right forum for this and I also searched for the past few days and have had no luck finding anything much on this. Most stuff I come accross is talking about the phone having a built in fm transmitter that doesn't work - blah blah blah. So here goes, I'm now on Paul's Froyo ROM and for the first time decided to try using the phone for playing music in my car thru a wired fm transmitter and it was not good. I now have three fm transmitters (2 I bought and the final one my brother gave me his that he used to use in his car with no problems) all give me the same results which is it seems okay playing through parts of songs that don't have much bass but once bass starts to hit it gets all awful stattic sounding and the Stereo (ST) indicator on my radio blinks so somehow the sound quality goes all bad. I've narrowed it down to obviously being something with the phone somehow cause I've tried with iPhones and another MP3 player and they (FM transmitters) work perfectly. I've also tried it with IntersectRaven's and CM's kernels for Froyo to see if the kernels might make a difference and no luck. So my question is, is this a known issue with the N1 or is this an issue with Froyo and isn't the case with say CM 5.0.7.1, anyone with experience can shed some light? Was thinking to go back to CM but after seeing all the threads of the issues in doing so decided not to but if this is not the case with other ROMs then it would make me switch back until a official Cyanogenized Froyo is out. If this is the wrong forum then my apologies and Dev's plz move to correct forum.
Update: I've messed with it some more and have been able to get it to play fine with Pershoots kernel but I have to turn down the media volume to approximately 70%. So it seems to me that with the media volume up all the way it must be drawing too much power or something from the headphone jack to make the output all distorted. I haven't tried with IntersectRaven's kernel to say if I get the same result since I'm just happy the darn thing works now. I'll also do a post in the Develoment forum linking to this in case anyone there may want to investigate this issue.
Click to expand...
Click to collapse
what you are describing is quiet normal if you drive the input of the fm transmitter too hard. You even found out the solution; lower the volume.
Yeh, but the thing that was baffling me was that the iPhones I tried worked fine with volume blasted and so did a MP3 player and that was with 3 different FM transmitters. I originally thought it was the transmitter so that's why I ended up buying another one to try then asking my brother for his which I know he used to have running with no issues. But after thinking about it for a while and searching some more I found posts in the kernel threads about audio boost so that's what made me think to turn the volume on the phone down.
Would like to try a vanilla kernel if you can link me to where to find one that's compatible with Froyo.
And actually I think I'm using CM's Froyo kernel but from what I understand it has pretty much the same tweaks as Pershoot's. Also need to go back to IntersectRaven's and try again with the vol down a bit but I don't have enough battery life left to feel comfortable flashing it.
For the FM-transmitter that I use in my car it's actually stated in the manual that you should keep the volume at about 50% on the device as to not ruin the sound. So I guess this is quite normal and just means you have to adjust the volume on the car stereo a bit.
Kman Gymrat said:
Yeh, but the thing that was baffling me was that the iPhones I tried worked fine with volume blasted and so did a MP3 player and that was with 3 different FM transmitters. I originally thought it was the transmitter so that's why I ended up buying another one to try then asking my brother for his which I know he used to have running with no issues. But after thinking about it for a while and searching some more I found posts in the kernel threads about audio boost so that's what made me think to turn the volume on the phone down.
Would like to try a vanilla kernel if you can link me to where to find one that's compatible with Froyo.
And actually I think I'm using CM's Froyo kernel but from what I understand it has pretty much the same tweaks as Pershoot's. Also need to go back to IntersectRaven's and try again with the vol down a bit but I don't have enough battery life left to feel comfortable flashing it.
Click to expand...
Click to collapse
All kernels are compatible with froyo, just go to the kernels thread and find a sock one
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..
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with a 5th pin going high in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Wow, I thought it was just me/my phone.
github said:
Wow, I thought it was just me/my phone.
Click to expand...
Click to collapse
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
lithid-cm said:
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Click to expand...
Click to collapse
Thanks, I figured it's a common problem but it would be nice to find a good solution.
I haven't seen too much of a connection with particular roms causing the issue. When it was originally a big problem a few months back (before it stopped happening for me), it would act the same way on every rom I stuck on it.
However, I just switched from deck's aosp rom to Synergy not long before this started happening again, and the sense roms definitely make it much more of an apparent problem than the AOSP roms would.
Physically to stop the problem, I know it's related to the MicroUSB port and I may try disassembling it if it gets bad enough.
From another post on it: "It's pin 4, not 5 , 5 is ground in the usb cable, when pin 4 is grounded it puts the unit in dock mode."
I'd post a link to the pinout, but the system makes me too newb to post pin outs. (Just google kineteka microusb b)
The same thing happened to my phone yesterday and it is pissing me off. Will it eventually go away over time or is it a permanent issue. Meaning when it dries off will everything be ok. I'm thinking about taking it in since I have insurance and see if they will either fix it or swap it out. I'm going to wait a couple of days to make sure there is no moisture in there.
There is an app called NoDock that you can download to fix this. In my experience, it does not work with MikG (which is probably a Sense 2.1 compatibiltiy issue). I am running Deck now too, and so far no issue with the AOSP ROM. If there is an issue, I read on the NoDock market page that CM based ROMs have an option to disable, and thus NoDock is not needed in this case.
Hmm. I'd think an app could be written that would catch the intent and do nothing, as well as manually adjust car dock volume via the volume controls. Maybe. But I don't think any kernel-level edits are needed. Maybe a decent dev can write something like that for you (I couldn't). [Edit: looks like NoDock might be that app] Another thought that might be stupid: have you taken a can of compressed air to your USB port?
Also, just a friendly reminder, there isn't any development work posted here so instead of the development subforum, this really belongs in General, or maybe Q&A. As a general rule, new threads in this section are only for sharing work you've done. Not to pretend I'm a mod or anything, just wanted to warn you so you don't get flamed to death next time.
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
lithid-cm said:
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
Click to expand...
Click to collapse
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
mjhuffer said:
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
Click to expand...
Click to collapse
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
lithid-cm said:
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
Click to expand...
Click to collapse
I thought it was illegal to sell rooted phones period. Or is it only illegal to make extra profit just based on the fact that it is rooted. That isn't to say that someone will do it anyways. My brother, who is phone illiterate, just got a nexus s and I really like it. I heard that the GSM version will be the first phone to get ICS (ice cream sandwich) so that means the CDMA one will be next. I'm perfectly happy with my EVO except when dumb stuff like this happens. I hate myself for asking but you got any progress on the rooting of 4.24 and the newest Hboot. Has the source code for the new Hboot been released?
I had a similar problem however it was caused by me putting my phone in my car dock
I had to freeze/uninstall both car panel and dock mode for it to finally stop giving me a notification and blinking the screen on and off when I hit bumps
Soldering USB port
lithid-cm said:
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
Click to expand...
Click to collapse
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
chile62 said:
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
Click to expand...
Click to collapse
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
odd, i had this same problem, what fixed mine was flashing a new different nv, it stopped it almost immediately
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
loose usb port
mjhuffer said:
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
Click to expand...
Click to collapse
The 4 points only hold the usb plug on to the board, on the backside of the plug, is where the actual connections are being made. They are almost like spring loaded connections.
When the soldered points get weak, the usb gets pulled pulled away from the mother board and some of the pins will not make contact.
Ed
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
This is crazy mine an my girls phones are doing this we bought a charger off of eBay an that's when it started I tried titanium pro an froze car mode seems to work but just a bandaid
Sent from my PC36100 using XDA Premium App
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect dock support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
Click to expand...
Click to collapse
Thanks man I'm going to wait for some dev to jump on this. Hopefully someone can create a .zip so you can flash it over any kernel. I would really just like the stock kernel with this option added in.
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?
Hey guys, Im new and might be getting a Xoom soon. I plan on using it to replace my car stereo. I already have speaker/sub amps and will use a 1/2 din equalizer to adjust volume and config inputs and whatnot. Basically, I have no idea where to look for software to make my own custom UI, rather than just having a tablet shoved in my dash, like the other installs I have seen. I have built many computer systems, mainly for gaming and I have also done custom stereo installs, so I know I can do this once I find what I need to research. Im not trying to be lazy and get all the answers, I just need pointed in the right direction. Thanks guys