Database Info

Car dock audio problem with Froyo 2.2

I just recently popped my phone's cherry and unlocked the bootloader so that I could get Froyo on my AT&T Nexus One. Before the update I had setup my phone to plug into a car dock with a headphone out to auxiliary jack to my car speakers.
The volume was consistently good to my car stereo when unplugged from the dock and when plugged in before the update. Now, immediately after I plug in my phone to the dock with the headphone jack pushing media audio my volume is reduced by 10-20%. I have disabled the dock managing my media audio, put everything to max volume on phone, and it still reduces the audio as soon as I plug it into the dock.
Does anyone else have a similar setup? I realize mine may be unique and I'm on my own. Are there any deeper phone settings to check beyond the standard volume controls?

Yeah I have the same problem. And my phone doesn't pick up my voice with voice commands and auto brightness doesn't work with the phone in the dock. Makes me wanna go back to Eclair...

Still have not resolved this by any means available. Maybe the official ROM will fix this issue. Also my paid apps still have not shown up and I am noticing that when I pick up inbound calls people cannot hear me for a few seconds.
I was hoping by this point in June that the official Froyo for N1 would have been released and there would be a ROM floating around but no such luck!

I've had a similar problem when my phone is docked with the car dock. In-call volume is extremely low, but other types of media are fine (i.e. music, navi, etc). My volume settings are maxed out too. I hope the official Froyo release fixes this problem. I use my car dock on a daily basis.

Looks like frf83 did not fix it. Car dock is useless for me. Seeing comments frome google that indicate they optimized for the cheesy built in speakers and hosed using the headphone jack while docked.
Pandora during the commute keeps me sane, and this ruins it. No froyo for me until this is fixed.

What I've discovered is when I car dock the phone media volume gets set to 12 out of 15 on the headphone jack. The volume setting GUI doesn't show that the volume has changed. Changing the media volume in settings doesn't affect the volume until I undock the phone.
Unfortunately for me that's too much output for my car stereo and music gets pretty distorted.
I downgraded to OTA ERD79 and the volume would remain the same when docked. I upgraded to the latest OTA and the max volume setting returned.

Having the same problem. At least I found this problem is due to Froyo, not my car dock.
Still, wished the USB port is still open while docked so I can bypass the Car Dock's circuits and just use it as a holder only.
Haven't rooted my phone yet, but if the devs can fix the issue on a custom ROM, I will root.

i used to have this set up where my phone was hardwired to the radio and after froyo i have noticed this problem too. I have now gone back to using a bluetooth connection (kensington liquidaux) and it seems to not have the problem.
for those following the other thread regarding the degradation of quality not just the low volume (double sucky). the bluetooth connection seems to not suffer the same fate.

agentkalaw said:
i used to have this set up where my phone was hardwired to the radio and after froyo i have noticed this problem too. I have now gone back to using a bluetooth connection (kensington liquidaux) and it seems to not have the problem.
for those following the other thread regarding the degradation of quality not just the low volume (double sucky). the bluetooth connection seems to not suffer the same fate.
Click to expand...
Click to collapse
You're referring using Bluetooth vs AUX for the dock and car to communicate? I'm guessing most of us don't have that option on our cars.

Check out the Kensington Liquidaux. It is an aftermarket Bluetooth solution that lets you use any AUX connection.
Sent from my Nexus One using XDA App

seancneal said:
Check out the Kensington Liquidaux. It is an aftermarket Bluetooth solution that lets you use any AUX connection.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Seems like an overkill for $80, especially when I don't need any part of the mount.

cigar3tte said:
Seems like an overkill for $80, especially when I don't need any part of the mount.
Click to expand...
Click to collapse
The one I got was $29. (Edit: I looked all over and can't find it at this price anymore...shoulda bought two!) It just included the cigarette lighter part and a steering wheel remote.
Sent from my Nexus One using XDA App

I have been waiting for a solution and still have not found one. I installed the latest Cynogen V6.0.0-RC1 and when reconfiguring for my dock I got full sound! I was greatly excited! Then... it dropped back down to its normal volume.
I need to figure out a way to disable the phone recognizing the dock entirely since I only use the dock for keeping it stable on my windshield and charging. Anyone have ideas?

norok said:
I have been waiting for a solution and still have not found one. I installed the latest Cynogen V6.0.0-RC1 and when reconfiguring for my dock I got full sound! I was greatly excited! Then... it dropped back down to its normal volume.
I need to figure out a way to disable the phone recognizing the dock entirely since I only use the dock for keeping it stable on my windshield and charging. Anyone have ideas?
Click to expand...
Click to collapse
I don't think the dots would pass through the charge if the phone completely stops recognizing the dock. This problem didn't start until Froyo, I'm pretty sure there'll be a fix for it.

I have the same problem. So much time has gone by since they released the car dock, first it was fine but after froyo the audio settings could not be saves anymore and the volume got much quieter.
No word from Google... nothing, no answer, no patch.
I'm really pissed, the car dock is almost unusable, except you go to audio settings every time you dock the phone and recheck the settings... :-(
there are already some people who reported the problem on the issue tracker. If you have the same problem please star the issue, but avoid giving "me too" comments... as everyone in the thread gets an email for your +1 comment.
http://code.google.com/p/android/issues/detail?id=10466
http://code.google.com/p/android/issues/detail?id=9073
http://code.google.com/p/android/issues/detail?id=8292
http://code.google.com/p/android/issues/detail?id=9747
http://code.google.com/p/android/issues/detail?id=8634
http://code.google.com/p/android/issues/detail?id=9445
google didn't even care to merge issues with the same topic... :-(
I really hope Android 3.0 (Gingerbread) will bring up a solution. (If the N1 will receive it)

Hi guys,
There's so many add-in tools out in the market that can easily solve those volume level issue. (e.g. "Dock Volume", "Car Dock v2", and many "Locale" or "Tasker" apps) So in my personal option, this is not an issue at all.

yang901 said:
Hi guys,
There's so many add-in tools out in the market that can easily solve those volume level issue. (e.g. "Dock Volume", "Car Dock v2", and many "Locale" or "Tasker" apps) So in my personal option, this is not an issue at all.
Click to expand...
Click to collapse
You're completely clueless to the issue at hand, please stay away from this thread. Most of those apps have been around before Froyo was even released.

Updated findings: Bad audio out thru headphone jack to car fm transmitter

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

[Q] Direct Connect for car stereo

Ok so some of you may know that a usb flash drive will play a lot louder and more clear than using bluetooth to listen to your music in your car. I can use bluetooth to listen to the music on my phone but when i plug it in to use it as a flash drive to listen to the music it says usb device not supported on my sony headunit. Even after i change it to disk drive mode.
Before i attempt to go into the kernel to somehow correct this do any of you know of a fix that would correct this? The reason this is important to me is that i have a sub in my car and a lot of the low frequency notes sound faint over bluetooth compared to playing it over a flash drive.
Ideally i would like to eliminate my flash drive entirely rather than finding songs i like but then having to transfer them to a flash drive to get better play-back.

Bump
Sent from my ADR6400L using XDA App

I also get the USB device error where I never did before on my old incredible. I am running an Alpine headunit. I wonder why its so much softer in volume over Bluetooth than USB.
John
Sent from my LogicPD Zoom2 using Tapatalk

Personally, I think it is the Bluetooth stack or hardware. My D2, the only thing I miss from that phone, had awesome range(100-200ft) and great SQ over BT. My TB only gets me about a 50ft range with the same sony mw600 bt module and subpar SQ. That is really my only true complaint about the phone. But, I deal because I love the phone overall.

yea that's what i thought...the only workaround i see is fixing this by allowing it to become capable with the headunit's usb device qualifiers somehow...i will work towards this...unless cm7 fixes everything and allows us to use it as a usb device lol...gotta love android

I had an Incredible and it worked fine hooking it up to the USB port on my Kenwood head unit. Once I upgraded to the TB I had a few issues. First the vcast drive that verizon installs on their phones interfere with the head unit reading the phone. It is the first drive that pops up wanting you to install software when you plug it into the computer. With the incredible you were able to access the phone menu and turn off the CD-ROM, but they took that access away on the TB. The only way I have found to get around that stupid drive is to plug in the phone to the USB port on the head unit with USB debugging turned on, wait a few seconds and then turn it off. For some reason this works to help my kenwood recognize the SD card and start playing music.

What is the advantage of this approach, compared to running an audio player on the t-bolt and going from the headphone jack to an aux in?

Better sound quality.
*EDIT* Plus you can control the music features through the head unit ie. skip, random, search, repeat, etc....

1454 said:
Personally, I think it is the Bluetooth stack or hardware. My D2, the only thing I miss from that phone, had awesome range(100-200ft) and great SQ over BT. My TB only gets me about a 50ft range with the same sony mw600 bt module and subpar SQ. That is really my only true complaint about the phone. But, I deal because I love the phone overall.
Click to expand...
Click to collapse
It's the bluetooth stack. Specifically the bitpool setting. It's set too low and to date all anyone ever says when I ask about a fix is, "Mine sounds fine".
CM7 should fix this since they use a different bluetooth stack than the stock one and set a higher bitpool.

dharper said:
I had an Incredible and it worked fine hooking it up to the USB port on my Kenwood head unit. Once I upgraded to the TB I had a few issues. First the vcast drive that verizon installs on their phones interfere with the head unit reading the phone. It is the first drive that pops up wanting you to install software when you plug it into the computer. With the incredible you were able to access the phone menu and turn off the CD-ROM, but they took that access away on the TB. The only way I have found to get around that stupid drive is to plug in the phone to the USB port on the head unit with USB debugging turned on, wait a few seconds and then turn it off. For some reason this works to help my kenwood recognize the SD card and start playing music.
Click to expand...
Click to collapse
Wow i really appreciate this man i will def. try this out. Did you have to put it in disk drive mode as well?

kkozma said:
It's the bluetooth stack. Specifically the bitpool setting. It's set too low and to date all anyone ever says when I ask about a fix is, "Mine sounds fine".
CM7 should fix this since they use a different bluetooth stack than the stock one and set a higher bitpool.
Click to expand...
Click to collapse
Yea the users that say "mine sounds fine" obviously do not have custom audio equipement in their cars. having amps on your speaker in conjunction with a subwoofer allows you to hear a lot more from your music even the imperfections.

Either that or they listen to sonicly simple music... I listen to just about everything and there's a massive difference in sound quality when I listen to something that's simple like hip hop/rap versus heavy metal.

trendsetter37 said:
Wow i really appreciate this man i will def. try this out. Did you have to put it in disk drive mode as well?
Click to expand...
Click to collapse
Yes. When you initially plug in the phone select disk drive. Then go to settings and turn on USB debugging. Wait a few seconds to allow the head unit to register the action on the phone and then turn USB debugging off. After this you shouldn't need to mess with anything on the phone.
It is a hassle to do this all the time when I am constantly getting in and out of the car, so I only use the USB feature if I know I am going to be in the car for a while. When I had my incredible I could reconnect and disconnect all day without touching anything on my phone. The only way I have found to disable it completely is if you are rooted you can go in and rename the CD-ROM.iso file, which essentially disables this drive from being accessed and not have to go through all this nonsense. I have yet to root the TB, and this is enough to make me want to root. I guess I am waiting to see if someone finds a better solution other than rooting to get rid of this Verizon nonsense.

I have yet to connect my phone to my car audio system. Will the imperfections have me gnawing away at steering wheel?
Sent from my ADR6400L using XDA App

dharper said:
Better sound quality.
*EDIT* Plus you can control the music features through the head unit ie. skip, random, search, repeat, etc....
Click to expand...
Click to collapse
Okay, I can appreciate how the DAC in a head unit might be better than the one in a phone, but I'm skeptical that the differences can be heard above the road noise. Plus, most people play lossy mp3's in the car anyway. If the source was lossless, then perhaps the quality would be discernible.
Your latter point, tho, is valid - except in my case where I like to play straight through random albums. I never have liked random songs so much. It totally messes up great conceptual albums like Pink floyd and others. I suppose I'm a purist in my thinking that to play one random song from an album dilutes the band's artistic statement. Of course, pop generally doesn't apply here.

I noticed this as well. so i just decided to use the standard aux cable through the headphone port.
occam's razor.

I can't seem to rename that file even with a root file manager. How do you do it?
Sent from my ADR6400L using XDA App

Direct connect Works!
I repeat direct connect works! I flashed the new radio (ruu) and then my normal tesla coil 1.1 rom over that. Sat in the car because i was curious and plugged my phone into the headunit's usb port and it worked. Read the sd card and everything. I didn't think that leaked ota would have fixed this but apparently it has?

trendsetter37 said:
I repeat direct connect works! I flashed the new radio (ruu) and then my normal tesla coil 1.1 rom over that. Sat in the car because i was curious and plugged my phone into the headunit's usb port and it worked. Read the sd card and everything. I didn't think that leaked ota would have fixed this but apparently it has?
Click to expand...
Click to collapse
also I do not have to switch the debugging feature...I just put it in disk drive mode and everything starts playing....I think it even sounds better coming from the tbolt rather than a flash drive; but maybe i'm just partial to my bolt lol

Ecomaniac said:
Okay, I can appreciate how the DAC in a head unit might be better than the one in a phone, but I'm skeptical that the differences can be heard above the road noise. Plus, most people play lossy mp3's in the car anyway. If the source was lossless, then perhaps the quality would be discernible.
Your latter point, tho, is valid - except in my case where I like to play straight through random albums. I never have liked random songs so much. It totally messes up great conceptual albums like Pink floyd and others. I suppose I'm a purist in my thinking that to play one random song from an album dilutes the band's artistic statement. Of course, pop generally doesn't apply here.
Click to expand...
Click to collapse
I have used BT audio since I bought my Moto Droid well over a year ago. Yes you can plainly hear the distortion even over road noise. I have a Pioneer headunit with BT headset/audio built in. You would be surprised how easy it is to discern the difference between streaming audio (pandora) and decent quality mp3 (256k). The stock BT stack is prone to artifacts that come across midrange speakers as pops. You end up thinking you blew a speaker. Change source / song and all is well. While I personally can hear a small improvement in the overall quality of audio running CM7 on my old droid vs liquid rom on my TB it isn't much different.
By the way agree on Pink Floyd, comfortably numb has to be one of my favorite songs on a great album.

Persistant Volume Issue in Gingerbread

Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
open1your1eyes0 said:
Hmm maybe it's just me but I think I discovered the oddest bug ever. For some reason, the first sound I hear after like 30 seconds of idle is quieter than what I'm set to in the volume settings and then if I keep using the device without idle all the sounds are loud like normal after that first sound.
For example, I have the device locked with screen off for a while, I unlock the device and the unlock sound is really quiet, then I immediately lock it and unlock it again and now the sound is loud like normal. I keep doing that and it sounds fine each time after that, but as soon as I lock it and leave it idle for like 30 seconds or more and unlock it again, the unlock sound is quiet again.
Also this doesn't only affect the unlock sound, it affects everything, notifications, alarm, ringer, etc....and all my volume is set to maximum I even checked with a 3rd party app. The same thing happened on the previous 2.07 and 2.10 leaks, it's almost like Gingerbread introduced this weird "automatically lower master volume after idle mode". I can't seem to find any option that would affect it.
Click to expand...
Click to collapse
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.

I've noticed this as well. I didn't find it to be a big deal, but thought I'd share.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1

all i know is even with volume+ the volume sucks on this phone. my wife's lg vortex is 5x louder. we need a dev to look into this.

I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.

arunningpir8 said:
I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.
Click to expand...
Click to collapse
aosp roms are louder but not loud enough. we for sure need a volume boost. i cannot imagine it would be that hard to do.

I was just getting ready to start a thread about a possible volume booster.. I can't remember if it was the tb or fascinate i had it on but, adrynalyne had a program called drm i think in his roms that enhanced the volume.. the problem I'm having is the media volume.. I'm trying to listen to MLB at bat here at work but can barely hear the broadcast.
Sent from my ADR6400L using XDA App

Hmm volume booster does seem to be a good workaround idea but I think the main issue is the fact that the volume level automatically changes regardless of the volume loudness. If only someone might be able to figure out what this can be caused by.....
Also I noticed something interesting today. On some sounds it actually seems like it starts off quiet and then makes it louder while the sound is playing. It's hard to tell cause it's so fast but it's definitely noticeable in some cases.

On cm7 there is an option to play notifications and ringtone through the speaker (even though I thought they did anyway) but I haven't noticed the problem with that selected.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1

someone should look into the lg vortex volume and try to port the mod over. my wifes phone is 10x louder than my tbolt. hers is aosp too.

FYI, I have only tested this on the official leaks. No custom ROMs or AOSP yet. Though I'm quite tempted to find out if this occurs on other ROMs as well (especially AOSP).

open1your1eyes0 said:
Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.
Click to expand...
Click to collapse
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk

nelboy said:
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?

open1your1eyes0 said:
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?
Click to expand...
Click to collapse
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk

nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm I see. FYI, I also noticed this issue is extremely obvious when opening the phone dialer for the first time and just press like the number 1. You can hear for a split second as if it "boots up" the audio amplifier the dialing sound for the button grows from silent to normal volume. Then as you dial the rest it sounds fine. But cancel out of the phone dialer and back into literally after like as short as 5 seconds press a number on the dialpad again, you hear it making dialing sound quiet to louder and then normal for the rest of the dialing.
Such a bizarre issue, I really don't understand why this problem just occurred in Gingerbread builds if it's been absolutely fine on older Froyo builds. You would think something as obvious as this would be one of the first bugs they try to resolve. And it seems like it wouldn't be that hard also (assuming it's just a setting in the kernel coding or something).
FYI, if it helps anyone willing to look into it I found out the audio amplifier for the Thunderbolt is a TI TPA2051.
I am really hoping some of our higher up guys can take a look at this. I am really curious to know what (if anything) can fix this issue.

i do know the overall volume on sense roms are much quieter than aosp. what a waste of a good speaker. we for sure need a fix here.

It might not be as easy as it sounds. Audio can be handled quite differently from OEM to OEM. I'm not sure if the thunderbolt is using the native Android audio or if HTC is using their own implementation. You also have to throw the audio Codec into the mix. Here is a link that although it doesn't explain our specific problem, you can see the complexity and the inherent issues with Android audio http://groups.google.com/group/android-ndk/browse_thread/thread/1744088af0924ed9/7170773c13aabe2f i'm not sure about now but the general consensus with audio developers used to be that google needed to stop trying to implement fancy bells and whistles in the audio and get a good solid foundation to start with. Gingerbread was supposed to address some of these issues but I don't believe it did.
Anyway, i'm not positive but you may notice the problem more in gingerbread because there were quite a few changes in the native audio implementation.
Sent from my A501 using Tapatalk

nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Gingerbread Kernel Source for Thunderbolt just released: Link

I know this thread is old, but something i've noticed in regards to this. Im running a semi-stock ROM (xda-bolt), with a stock kernel. I noticed the volume changes don't happen on this ROM, however with a modified kernel such as IMOs 6, the problem arises. Any other non-stock kernel i've used has this problem, but stock kernels do not.

Double speaker mod

Its possible to add another 2 speaker to the tablet?
Space isnt a problem, i mean, its possible? did anyone tryed?
As all speakers works with + and -
its just easy to cut wires and split for another 2 speakers more
obviusly will consume more battery and of course will need more space
but its possible without ruining my tablet¿
(speakers pulled from old hp dv6 laptop)

tvm777 said:
Its possible to add another 2 speaker to the tablet?
Space isnt a problem, i mean, its possible? did anyone tryed?
As all speakers works with + and -
its just easy to cut wires and split for another 2 speakers more
obviusly will consume more battery and of course will need more space
but its possible without ruining my tablet¿
(speakers pulled from old hp dv6 laptop)
Click to expand...
Click to collapse
I would read about impedance and what happens when you connect speakers in paraellel as you are likely to over work the hardware trying this.

mike240se said:
I would read about impedance and what happens when you connect speakers in paraellel as you are likely to over work the hardware trying this.
Click to expand...
Click to collapse
these speaker i have are 4ohm independance but theres no info about gtablet speakers :S
do you think if i connect in paralellel i will blow out they? (four speaker)

mike240se is correct.
Not only that, but those 4 ohm speakers are going to be the worst you could add.
I never looked at the imp. of the speakers in the G-Tab, but these small speakers are usually higher impedance.
If you attach 2 additional 4 ohm speakers, you will mostly hear only them, that is if it does not damage the output circuitry.
Get a nice set of Bluetooth, or wired amplified speakers, it will sound much better, it is much easier, and there is much less chance of damaging your G-Tab.

I'm guessing you want to do this to hear better...? Just download one of the million volume boosters? I use Volume+ the paid one, its great.

Yamagushi said:
I'm guessing you want to do this to hear better...? Just download one of the million volume boosters? I use Volume+ the paid one, its great.
Click to expand...
Click to collapse
yeah louder

tvm777 said:
yeah louder
Click to expand...
Click to collapse
Yea just buy Volume+, its like 2 bucks. I set it to full boost at 20(Doubles the volume), usually have my tablet just over halfway and everything is nice and loud.

scends anuantit
Yamagushi said:
Yea just buy Volume+, its like 2 bucks. I set it to full boost at 20(Doubles the volume), usually have my tablet just over halfway and everything is nice and loud.
Click to expand...
Click to collapse
this app doesnt damage your speakers?

tvm777 said:
this app doesnt damage your speakers?
Click to expand...
Click to collapse
If you play something that's already really loud with everything maxed out, maybe. If you use common sense, then no lol. Doubling it makes half volume into full volume and beyond that is above 100%. I usually use it around 130%, but there are times with something like netflix were its so quiet I max it out to 200%. Its harmless. Any issues will be very audable. If its too loud, youll hear it crackling(badly, a small amount of distortion is normal) and such. Realistically I don't think you'll have an issue, just go by ear, if its loud enough to hurt the speakers, itll sound like crap and youll know right away.

Yamagushi said:
If you play something that's already really loud with everything maxed out, maybe. If you use common sense, then no lol. Doubling it makes half volume into full volume and beyond that is above 100%. I usually use it around 130%, but there are times with something like netflix were its so quiet I max it out to 200%. Its harmless. Any issues will be very audable. If its too loud, youll hear it crackling(badly, a small amount of distortion is normal) and such. Realistically I don't think you'll have an issue, just go by ear, if its loud enough to hurt the speakers, itll sound like crap and youll know right away.
Click to expand...
Click to collapse
thanks, ill download this app then

tvm777 said:
thanks, ill download this app then
Click to expand...
Click to collapse
No problem

Yamagushi said:
No problem
Click to expand...
Click to collapse
i tryed volume+, but seems doesnt work
volume isnt increasing
any suggestion?

In response to both of your posts, flash the teamdrh JB rom, it is really stable for an alpha, and for some reason, it is really LOUD!!!

redeyedjedi said:
In response to both of your posts, flash the teamdrh JB rom, it is really stable for an alpha, and for some reason, it is really LOUD!!!
Click to expand...
Click to collapse
I have already downloaded Jb teamdrh rom, but since i dont have full root access, titanium backup cannot backup anything
its there any other option to backup my applications?
i cant access to system even mounting usb trough cwm

try appmonster. But, i dunno if it will work. What I do know is if you use applanet, the downloaded apks are in the applanet folder. If you use google play store, then set your rom to backup your account and automatically restore, then after you flash a new rom, you can just restore your apps from online?? I think this is how it works, but I have never let google into my life that much!!
***a quick google search reveals that appmonster needs no root! so try it.
http://www.apkmania.com/2012/06/appmonster-pro-v252-apk.html

redeyedjedi said:
try appmonster. But, i dunno if it will work. What I do know is if you use applanet, the downloaded apks are in the applanet folder. If you use google play store, then set your rom to backup your account and automatically restore, then after you flash a new rom, you can just restore your apps from online?? I think this is how it works, but I have never let google into my life that much!!
***a quick google search reveals that appmonster needs no root! so try it.
http://www.apkmania.com/2012/06/appmonster-pro-v252-apk.html
Click to expand...
Click to collapse
do i need to follow all instructions carefully for jb teamdrh?
Download the following file <--- Seriously don't skip this step unless you are 100% positive that you have a 350M system partition (md5: 256a4bf1da503f4a1ec1f998a00a05f2)
Click to expand...
Click to collapse
already did! jb its on the way updating