yashsingh1/xdaforums huggingface dataset:
[Nook Color General] mr72:
Yes, I've read (or skimmed) most, or all, of the threads on this topic.

My NC audio is...

1. too bright, sibilant

2. lacking in bottom end

3. harsh/hissy in the top end

not talking about playback over the built-in speaker. talking about listening with high-end headphones (in my case, some Shure SE315s and also ME Electronics M6).

I'm not talking about the audio jack behaving differently according to how you insert the plug. Not talking about trying to get bluetooth audio. Not talking about Pandora sounding bad, or a lack of an equalizer on the Google Music player, etc.

Has anyone found a solution that will just fix the actual audio quality (as in, tone balance) issues?

edit:

BTW, I did find that using DSPManager (on CM7.1) it gets much better with a custom EQ setting (each band):

+1.0 +0.5 0.0 -0.5 -1.0 -1.5

The top end is still harsh sounding, but at least it's not overbalanced in this case.

This makes me think this is likely a hardware issue... too small or the wrong type of coupling cap somewhere.
[Nook Color General] mr72:
Perhaps you guys are not trying to listen to music on your Nook Color, thus the lack of discussion on this thread.

After comparing to my laptop and my HTC phone, I have discovered that at 100 Hz the NC is at least -10dB compared with my phone. This is extreme! I will try to do some FFTs of this over the weekend.

I think it's a hardware problem.

For the time being I have "bass boost" on DSP Manager turned on, along with some rather extreme EQ settings. It still sounds bad, but at least it's not ear-bleedingly bad.
[Nook Color General] NRGZ28:
I've noticed this too with other "lower end" devices, or devices where the engineers aren't too overly-concerned with its audio quality. They usually don't sound the best. I'm sure it's not just your imagination on this. And to think I was actually considering getting a nook as a cheap in-car entertainment device... ugh :(
[Nook Color General] mr72:
I don't think it's because it's "low-end".

I think one of a couple of things may be at play here.

1. the NC is intended to play only through the internal speaker and/or only play audiobooks (spoken word only). So they intentionally rolled off the bottom end (and most of the midrange as well).

2. audio was not even on the minds of the engineers of the NC, so they didn't bother to check what value coupling capacitors or filter components will work correctly

3. the software/driver is programming the audio device with an extreme HPF intentionally

The reason I don't think it's just because it's "cheap" is because a $20 MP3 player will get all of this right. In fact, it's almost trivial to get this more than good enough. The rest of the NC hardware is way more well-done than this. This screen would not be on a "cheap" device where they severely cut corners on audio by oversight.

So my suspicion is that the audio behavior of the NC is quite intentional. I don't know if it's HW or SW. I seriously hope it's SW.

Glancing at the datasheet for the audio chip (http://www.ti.com/lit/ds/slas671/slas671.pdf) I notice that the audio device has automatic headset detection. This does not seem to be implemented on the NC. Maybe that's the problem. It also has two audio inputs. The more I look at this, the more I want to crack open my NC. The datasheet suggests AC coupling the headphone outputs so there is some capacitor likely in series with each of these lines. IMHO this is the most likely culprit to the NC's crappy sound, if it is a hardware problem. In this case it's only two components to swap, should be a snap. But I don't really want to solder on my NC.

The DRC (dynamic range control) does have a HPF that might have the ability to cause this crummy sound in software, but I doubt it. However, it would not surprise me for the NC developers to turn on some DRC all the time.

I guess I really need to get at the source code of whatever the driver is for the audio device, or get a busted NC so I can trace the output circuit and determine if it's a hardware issue.

Or maybe I'll just not use this to listen to music and watch movies.
[Nook Color General] mr72:
OK. This is quite strange.

For a quick experiment, I did a FFT on pink noise playback from my Nook Color, my HTC Aria phone, and my computer's sound device (in this case, Tascam US-144).

Now, of course I am not playing this into HEADPHONES. In fact, the input of my US-144 "Line In" that I used to test this is AC-coupled and about 50K ohms.

Into that impedance, the output of the NC looks pretty freakin' flat. Moreso than my phone, in fact. So this is good news for you guys wanting to use a NC to plug into the Line In on some device. There is nothing wrong with the audio. It looks great.

However, since my ears, with my earphones, told me that the NC's output was anything BUT flat, I decided to do another test. This time I clipped in an 8 ohm load across the output, to see what the NC's frequency response looks like into an 8 ohm load. I did this also for my phone for comparison.

The NC's output is about -25dB at 100Hz going into an 8 ohm load (typical headphones are maybe more like 16 ohms). As you can see, this is hugely different from the 25K load output.

The verdict? The NC's output is very reactive according to what load you attach to it. Plugging in most headphones will result in a huge roll-off of the bottom end. You could plug it into a buffer or external headphone amp and it would probably sound just fine.

And for comparison, I did the same test with my HTC Aria, and the 8 ohm output looks pretty much exactly like the no-load output. The Aria is a teeny bit lower in the sub-100Hz range than the NC into no-load, ant it is pretty much exactly the same into an 8 ohm load.

After making this discovery, I am more inclined to think this is a hardware design problem, with the output coupling caps being too small.

Armed with the frequency response curves, I experimented with DSPManager EQ settings to try and come up with an EQ that gets it close to right into an 8 ohm load. It is impossible to do it.

However, with DPSManager's "bass boost" turned on, and "Moderate", and EQ settings of +10, 0, -10, -10, -10, -10 it gets to "flat" but not "pink". I am guessing it's distortion showing up at the top end.

In all, this kind of sucks.
[Nook Color General] TonyBigs:
Thank you for the info. I would look at the coupling capacitors as well. If they're Tantalum I would replace them with Aluminum Oxide and ensure the capacity is at least 220ufd. The problem would be finding the room. In some experiments I did years ago repairing a portable CD player, Tantalum did awful things to high frequency reproduction.

EDIT: here's a picture of the audio circuit on the motherboard (both from ZDnet):

NOOK COLOR

I cannot identify what I would think are the two headphone coupling capacitors. I suspect they are very small value. They *look* like ceramic (color, no polarity markings) and if so, they would be marginally suitable for a line out and sonically and electrically useless for headphones for music listening.

To contrast:

NOOK TABLET:

I am assuming the large two black capacitors side by side are the headphone coupling capacitors. I do believe these to be tantalum electrolytics (color, polarity markings, shape).

S 7 j e

Trying to interpret that code.

My best determination is 47uf @ 16v -- the "j" may be a tolerance code.

If that is the case then 47uf is way too small of a value for any strong bass output at low impedances (16-32ohm). Minimally acceptable at best.

Color and Tablet:

Both circuits seem to have a very small (pf) capacitor after each coupling cap as a high frequency roll off filter. Not unusual for portable equipment if the capacitor value isn't too large causing excessive rolloff.
[Nook Color General] zires:
You sir are a star! So an amplified set of headphones is the key?
[Nook Color General] TonyBigs:
Possibly. I still think there would be issues with Nook's coupling capacitor type and value but the input impedance of the headphone amp might overcome the frequency response issue. Sound quality and noise may be another problem that the headphone amp might not address. Tantalums are not good for sound. That is, garbage in, garbage out.

There may be other problems concerning the configuration of the sound chip in the firmware. The TI chip is capable of a lot of sonic "tricks" but based upon your graphs maybe the sound isn't too compromised in the firmware.
[Nook Color General] mr72:
Hard to tell if those are the headphone output coupling caps without tracing the circuit or at least being able to see the alignment dot on the component package of the audio chip. However, if those are the headphone output caps, then they are followed by a ferrite bead and parallel caps most likely to trim off HF noise as well, evidenced by just looking at the pic.

The Nook Tablet pic definitely has bigger caps, probably tantalum, and who knows the value but that's not a 7343 package, so it can't be more than maybe 100uF.

Looking at the FFT, it looks like about a 1KHz Fc into my 8 ohm load, so I am guessing the caps in a NC are more like 22uF. 220uF still gives like 90Hz Fc into 8 ohms, down to 45Hz into 16 ohms. To get full bandwidth into 16 ohms is going to require about 470uF. Maybe compromise at 330uF and hope you have bigger impedance cans.

Those look like 1206 packages on the NC and 1812 package on the NT to me. Even a tantalum at 470uF is going to be a whole lot better, if this is in fact like 22uF. However, finding an 1812 cap at 220uF or 470uF may be extremely difficult. I am not going to argue about putting a different material cap in here because it's just way too small. A brief check of Mouser shows 7343 is the smallest 470uF caps even at 2.5V in tantalum. They have 6032s in 330uF. But those are way too big.

How hard is it to get the NC apart to the point at which this picture was taken? Do you have to unsolder any components to get there?

I wonder if there is any DC on those outputs, or whether these caps can just be jumpered.

The datasheet says the headphone outputs are rated to drive a 16 ohm load. I guess I was overloading them a little into 8 ohms.

After scanning caps, I think it's pretty much impossible to find a reasonable value cap that will fit into a 1206 or 1210 SMD space. Even the 1812s on the NT are not nearly big enough size-wise. So the only way to solve this with hardware mods is to either put caps somewhere in the wiring between the jack and the board, and jumper the caps on the board, or just jumper the caps on the board and hope for no DC on the outputs. Looks like a good time to use an external headphone amp, or noise-canceling headphones (have a built-in amp).
[Nook Color General] mr72:
BTW, here's the cheapest, easiest solution to this problem:

http://www.amazon.com/Fiio-E3-BK-E3-Headphone-Amp/dp/B001MPWMDA

And if I were to crack open my NC, rather than doing any surgery or trying to cram different caps in there, I would do this: take the whole PCB from an E3 and shoehorn it into the NC in some open space, wire it between the headphone jack and the headphone output on the NC PCB, and pick up some power from the NC somewhere to run the E3.
[Nook Color General] hwong96:
Have you installed Dalingren's Nook Tweaks from the market? You can adjust audio settings using this app, specifically increase DAC, adlust headphone gain, speaker gain. Warning! Increasing DAC too high will damage your speaker. I have my DAC setting about 5/8 inch from the left under the a and s in the word "increasing".
[Nook Color General] mr72:
Yes, this is not a volume problem. It's a frequency response problem, related to the impedance of the device connected. Please see the plots.
[Nook Color General] 22jjones:
I posted earlier about my solution to this. By no means cost effective or portable. FiiO E7 USB DAC and CM7. I stream and download 320 bit from MOG. Great for me working hours at desk. Download is unlimited and can listen offline. The audio quality with this little rig is superb. As in unbelievable. I also use good headphones.
[Nook Color General] mr72:
You using this with USB Host Mode? Is it drawing power from the USB?

Certainly this will sound good but like you say, it's hardly portable. Now, if it were bluetooth rather than USB...

I think a FiiO E3 or E5 headphone amp will mostly fix the main problems, while not improving the DAC or noise performance any. It will definitely fix the reactivity of the output stage. Plus an E5 is cheap + rechargeable and an E3 extremely cheap and extremely compact, barely noticeable and perfectly portable.

I plan to use my NC to read, listen to music and watch movies while on long plane rides, which are all too frequent with my job. Long battery life is key (so drawing power on USB host mode may be bad) and noise performance is not critical. For this kind of thing, I think a small external headphone buffer amp is the ideal solution.
[Nook Color General] 22jjones:
No power drawn from USB, the FiiO has it's own rechargeable battery, one charge will last much longer than the Nook. You have to turn charging off on the FiiO while plugged in to Nook. It is using USB host mode. Add Sennheiser CXC 700 ear buds, and the rig is entering into the audiophile zone.

I think you're right, a small headphone amp, and some EQ will be good. I just did my setup as kind of a quest on how far I could go with Nook audio!
[Nook Color General] bluespire:
That E3 also notes it's for 16+ ohm devices. How does that fix it if you are using your 8 ohm headphones?
[Nook Color General] mr72:
The two pair of earphones I will be using are 16 ohms and 23 ohms. I tested the NC's audio output into an 8 ohm load simply because that's the practical lower limit for headphones. They are much more commonly 16 ohms or more.

However, to answer your question specifically, it probably doesn't matter, but it's not worth getting into here. The LM4917 amplifier used in the FiiO is rated at 95mW into a 16 ohm minimum load. Running into a smaller load will just limit the maximum voltage swing or increase distortion when the amplifier is running on max.

FWIW, I think I could probably dead-bug a LM4917 into a NC easier than cramming big output coupling caps in there. That'd fix it as well.
[Galaxy Ace S5830 General] acesteady:
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,

Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.

Okay this is the problem

I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6

And I found there's no problem with touchscreen and then I did the GingerCrust v2.3

And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)

I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test

but the code won't work

and I tried to find additional framework on it's official thread(by nims11) but there's none of it.

Did anybody have a problem like me? Is there already a solution for the problem that I found
[Galaxy Ace S5830 General] nims11:
Thats new bug you phased not anyone tell about and not im phasing any that thing

v2.2 and v2.3 are almost same just few things like odexed and some fix not much other thing
[Galaxy Ace S5830 General] adeklipse:
I have this problem also.

It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.

For example, I write "I love you", it will turn out as:

"Ids sdldovsed ysdous"

or something like that. Very frustrating.

I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem. :(

Sent from my GT-S5830
[Galaxy Ace S5830 General] adinq:
I got this too http://xdaforums.com/showthread.php?t=1271268
[Galaxy Ace S5830 General] CambaStorm:
I don't have that bug... did you flash the framework for v2.2 before flashing 2.3? maybe this dosn't afect to the touchscreen but just only to see what was your flashing process.
[Galaxy Ace S5830 General] acesteady:
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.

@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://xdaforums.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!

@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
[Galaxy Ace S5830 General] nims11:
moded framework allready gave in rom

touchscreen prob of keypad you tell is not happen atall in my phone

Im reply all things from my phone not from pc means not phasing that stuff yet

will try to solve for those phasing in new version
[Galaxy Ace S5830 General] acesteady:
thanks for the quick reply nims, just info for you the bug that I found is just exactly the same as adeklipse said
[Galaxy Ace S5830 General] icemanhi:
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://xdaforums.com/showthread.php?t=1296905 and the problem is gone.
[Galaxy Ace S5830 General] adeklipse:
And "#throwinag##"% fthus akernael wdill make it wsorks,h rigsht?

This is the text that I typed without any correctionss

And "throwing" thus kernel will make it work, right?

Sent from my GT-S5830
[Galaxy Ace S5830 General] adeklipse:
Sorry for the dopost.

I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.

I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.

So possible solutions are:

1. Underclock to <800MHz (for max clock)

2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).

Sent from my GT-S5830
[Galaxy Ace S5830 General] acesteady:
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that :D

matur nuhun.......
[Galaxy Ace S5830 General] adeklipse:
Yep, I went with flashing the non-oc kernel as well. Underclocking will still leave you with the problem.

Sami-sami. :)

*ane orang Banjar nyasar ke Bandung, gan.

Sent from my GT-S5830
[Galaxy Ace S5830 General] musf:
I use 800 MHz on oc kernel and not facing this problem.. maybe I'll try above 800..
[Galaxy Ace S5830 General] adinq:
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM

2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT

Can somehow fix this without reducing the MHz to 700? :(
[Galaxy Ace S5830 General] adeklipse:
Yes: reduce to 800MHz. Though I still have some problems with that.

Sent from my GT-S5830
[Galaxy Ace S5830 General] prodal:
I also have the same Problem.

It was all fine with froyo 2.2, when i switched to stock 2.3.3 kpe or 2.3.4 kph this problem occured. It stopped happening with 2.3.3 kpy and its perfectly fine with the 2.3.5 stock firmwares.

My big problem is, i cant use any custom roms, it happens with every single custom rom.

So it's not really a warranty issue when it happens with custom roms. Coz samsung could say it works fine with stcok firmware, 2.3.3 kpy for example.

I really don't know what the cause of the problem is, because my friends galaxy ace doesnt have these problems with the custom roms i tried.

I'm not sure but besides the kernel i kinda think it might be a battery issue, because it happens less frequently when its plugged to the charger.
[Galaxy Ace S5830 General] udhien28:
may be this mod can help you..

http://xdaforums.com/showthread.php?t=1365434

i OCed to 883MHz without problem on touchscreen :)

matur nuwun :)

aku wong solo bro...╋╋ム ╋╋ム ╋╋ム =)) ╋╋ム ╋╋ム ╋╋ム

pls press thanks button if you like this.

sorry for my bad english
[Galaxy S I9000 Q&A, Help & Troubleshooting] alandd86:
i have a problem which is whenever my phone goes to sleep for a bit long time and some1 call after that then my phone freezs and force close,, what should i do plzzz

thnxx :confused:
[Galaxy S II General] KunalGautam:
Recently one of my friend blogged about increased time at Andorid Market. I tried it and I was all yay! because it really worked :D

Read more about it at http://knowmydroid.com/blog/android-market-app-refund-time-increased
[Galaxy S II General] skimminstones:
still not enough for me. For example if you buy a sat nav on the market, How are you supposed to download the maps and test it works properly in 30 mins? JUst encourages people to get the pirated versions instead.
[Galaxy S II General] markp1989:
a step in the right direction! but still not enough.

I miss the 1 hour refund policy, not i dont buy as many apps as I dont wanna be stuck paying for one after it doesnt do what I need it to.

I would like a 1day return, that way I can properly test the app. some times I have brought an app that I liked, but it killed the battery over the course of a few hours so I uninstalled it, but I still had to pay for it.
[Galaxy S II General] mad2fly:
I suppose if you were to test an app with a pirated version, there would be nothing stopping you from then going to the market and paying for it if it worked for you.
[Galaxy S II General] buzzboy:
Wow that's generous.!

(Sarcasm mode off)

But I agree with the previous comment, it's a step in the right direction.

Ah, I remember the good old days.

Regards
[Galaxy S II General] marcadam:
We should also get a warning when you try and install an app for the second time, I can't always remember what I've tried.
[Galaxy S II General] KunalGautam:
I remember all horrible apps O_o
[Galaxy S II General] alias_neo:
If devs got off their arise and used market licensing, which I promise is a breeze to implement, piracy wouldn't be a concern. If its not the current concern its probably potential loss of money on Google's part and that's their only concern.
[Galaxy S II General] Mittaa:
Hi

Most apps prices are relatively low so in most cases it's not a big problem that will ruin you :)

But 30 min. is still a very short period, and I sadly have to admit that I have bought several apps that I never use.

Worst case for me was an expensive Copilot Live Premiere EU that I seldom use :(

It would be nice if we had some kind of return right in case app is too buggy :rolleyes:
[Galaxy S II General] vcosmin:
at least we have 30 minutes...

others don't.

look on FAQ's on their market or whatever the name:

What is the Mac App Store refund policy?

If you experience a technical issue with an app, first contact the developer of the app for assistance. Their support contact information can be found on the app's page in the Mac App Store. If that does not resolve the issue, contact Mac App Store Customer Support.

that's crap
[Galaxy S II Accessories] spd2230:
Like the title says...

I purchased an SGP case for my AT&T S II and they included both screen protectors.

I have no need for the protector for the international version.

First "I'll take it" gets it and I will pick up postage, just PM me your name and address.
[Galaxy S II Accessories] SirM2X:
I'll take it
[Galaxy S II Accessories] spd2230:
SirM2X,

PM your name/address and I'll ship it in about an hour.

Enjoy!