I'm running DamageControl on my HTC Hero (Sprint) and all of a sudden my ear speaker sounds like its blown! I have never had it on max volume because I have excellent hearing and don't need it that high. Also when I talk I can hear myself echo through it. It sounds TERRIBLE.
What could have happened? Going to do a nandroid and restore Fresh 2.0b2 and see if its still happening.....
JUST A NOTE: DAMAGECONTROL DID NOT CAUSE THIS TO HAPPEN TO MY HERO. I AM ONLY NOTING THAT I AM RUNNING DAMAGECONTROL, NOT THAT IT BLEW MY SPEAKER
Cause derp.
MrTrip said:
I'm running DamageControl on my HTC Hero (Sprint) and all of a sudden my ear speaker sounds like its blown! I have never had it on max volume because I have excellent hearing and don't need it that high. Also when I talk I can hear myself echo through it. It sounds TERRIBLE.
What could have happened? Going to do a nandroid and restore Fresh 2.0b2 and see if its still happening.....
Click to expand...
Click to collapse
might be the hardware...you should be able to exchange at sprint store.warranty.
http://androidforums.com/sprint-htc-hero/17137-speaker-blown.html
Well, I guess there is my answer. I bought the phone from Radio Shack, will this be an issue when taking it to a sprint store?
depend, after 30 days you can bring into sprint(with TEP much easy/less hassle)before 30 days you can bring back to the shack...i exchanged mine all the time.i have insurance which took care of everything.Mostlikely if tech at sprint cant fix it(most likely they wont fix it) then they will order you a new one....good luck.
Flashed back to Fresh 2.0b2 and still had problem, used my air compressor and blew the crap out of the speaker, tada it works. I'll hit up the Sprint store tomorrow though.
QUESTION:: I should probably revert my phone to stock eh? How would I go about doing this WITHOUT RUNNING THE RUU...That is a scary bastard to run after the other threads around here.
MrTrip said:
Flashed back to Fresh 2.0b2 and still had problem, used my air compressor and blew the crap out of the speaker, tada it works. I'll hit up the Sprint store tomorrow though.
QUESTION:: I should probably revert my phone to stock eh? How would I go about doing this WITHOUT RUNNING THE RUU...That is a scary bastard to run after the other threads around here.
Click to expand...
Click to collapse
RUU is the only way... otherwise you stay rooted.
MrTrip said:
Flashed back to Fresh 2.0b2 and still had problem, used my air compressor and blew the crap out of the speaker, tada it works. I'll hit up the Sprint store tomorrow though.
QUESTION:: I should probably revert my phone to stock eh? How would I go about doing this WITHOUT RUNNING THE RUU...That is a scary bastard to run after the other threads around here.
Click to expand...
Click to collapse
You could revert back to the nandroid you should have made right after you rooted but before you flashed any roms. I highly doubt that sprint is going to check deep enough into your phone to realize that it is rooted. If they take it and give you a new one they will fix it, wipe the old OS, flash the stock 1.5 rom, and push it out their door to the next person that needs a warranty replacement.
robchaos said:
You could revert back to the nandroid you should have made right after you rooted but before you flashed any roms. I highly doubt that sprint is going to check deep enough into your phone to realize that it is rooted. If they take it and give you a new one they will fix it, wipe the old OS, flash the stock 1.5 rom, and push it out their door to the next person that needs a warranty replacement.
Click to expand...
Click to collapse
Well, thing is I made that nandroid backup, and then I accidentally flashed my SD card, so I have no original 1.5 backup (heh whoopsies?) that was back when I was super noob....sooooooooo flying by the seat of my pants here. BUT GOOD NEWS IS 2.1 IS SO FREAKING FAST AND STABLE IT MAKES MY PHONE A SEXY MAN BEAST AND WHY WOULDN'T SPRINT WANT A SEXY MAN BEAST PHONE I MEAN COME ON?!
I'll give it back to them running Android Home with Live Wallpaper turned on. Really make them go "....Huh?"
Nah, I'll wait for it to fritz again and flash the first decent looking 1.5 rom I can find.
I have this same issue, and it did not start until I did flash Damage as a matter of fact. I thought I was making it up and being too OCD. Hey dude, after you RUU back to stock let us know if the problem still exist.
the same thing happened to me. brought it to a Sprint store and they replaced it for free
Ska8erMush said:
the same thing happened to me. brought it to a Sprint store and they replaced it for free
Click to expand...
Click to collapse
After flashing to 2.1? What did it sound like for you?
Tipharet said:
I have this same issue, and it did not start until I did flash Damage as a matter of fact. I thought I was making it up and being too OCD. Hey dude, after you RUU back to stock let us know if the problem still exist.
Click to expand...
Click to collapse
I just blew it out with an air compressor, 60lbs pressure output, and it fixed it. Went back to DamageControl rom and everything is ok so far. Maybe the software on the rom outputs too much to the ear speaker? Maybe the Nexus One has an earpiece speaker able to handle louder noise? I don't know... Being a nix core, you can easily put too much power to something....
Somebody correct me if I am wrong?
I have heard that dust gets in the speaker and clogs it up. Saw a thread on Sprint a while back. I had the same thing happen to my phone and they replaced it no problem. That was before 2.1, so I doubt the OS has anything to do with it. Again, probably dust, the speaker does have a lot of open surface...
This has nothing to do with the 2.1 ROM. Me and many others had the same issue while running stock firmware. I got a brand new hardware v.2 Hero out of it.
danknee said:
This has nothing to do with the 2.1 ROM. Me and many others had the same issue while running stock firmware. I got a brand new hardware v.2 Hero out of it.
Click to expand...
Click to collapse
Oh? How do I check what Hero I have?
MrTrip said:
Oh? How do I check what Hero I have?
Click to expand...
Click to collapse
Menu >> Settings >> About Phone >> Hardware Information
or you can look at the battery cover, if it says "with Google" it is V.2 if it doesn't it is V.1
mine blew out when i was running 1.5. Still waiting for a replacement 4 weeks later.....
beyondinferno said:
mine blew out when i was running 1.5. Still waiting for a replacement 4 weeks later.....
Click to expand...
Click to collapse
I took mine in to a Sprint repair center, they verified the speaker had an issue and they placed an order for a new handset. It came in 24 hours later and we swapped my broken unit in for a brand new one.
I bought this phone directly through Sprint online, not sure if that matters. The whole transaction was smooth for me.
Ska8erMush said:
the same thing happened to me. brought it to a Sprint store and they replaced it for free
Click to expand...
Click to collapse
replaced the speaker or the whole phone?
If anything, DamageControl1 seems to handle loud audio better than the stock 1.5 Sprint ROM did. I have a few mp3 files I put on my phone to use as possible ringtones with RingDroid that sounded too bad to use with 1.5, but actually sound quite good now under DC1.
Theory #1: 1.5 rendered the mp3 to pwm without regard to the nonlinear frequency response of the phone's electrostatic speaker. 2.1 runs it through a DSP companding altorithm to concentrate the sound's volume in the bands the speaker can reproduce well, and attenuates bands the speaker can't handle well. Net result: louder perceived output with fewer artifacts.
Theory #2 -- 1.5 did a hack job on the audio before sending it to the speaker, and arbitrarily clipped it to some max ordered by Sprint's upper management or legal department, whereas 2.1 either goes out of its way to properly compress the dynamic range, or (being open source, and having its kernel parameters dictated by concerns of audio fidelity rather than paranoid theories of legal risk) simply doesn't care, and sends the rendered audio straight to the speaker without further mangling
I'm assuming that both ROMs do mp3->PWM entirely via software, and the Hero has hardware codecs only for hardcore things, like video (and even then, only for things like the acceleration of inverse discrete cosine transformations).
Related
So I love this phone. I received it yesterday, and I can get a very accurate GPS lock in about three seconds, without the 'fix'. I havent noticed a single problem with the phone. The only thing I have a question about is this 5.1 Channel Surround Sound. It says you can only use it in headphone mode-but when I put in the headphones that came with the Vibrant the only thing I notice is it makes the movie/music higher pitched. Is that all it does or am I missing something?
It's an SRS sound processing effect, best for movies since you can't adjust the "TruBass", "Dialog Clarity", "Center/Surround" or "Focus"..
IMHO some of us would be loving a true SRS iWOW DSP, and not this crap Samsung gave us. It's best left off for music and it probably isn't that great for movies
Boy, ain't that the truth!
If there is some developer out there PLEASE port SRS WoW to
the android platform...!
Or at least give us some way to set the sound options on the
video player. I really like this phone but, even with headphone on
it's sometimes very hard to hear movies while they are playing.
alecjake said:
So I love this phone. I received it yesterday, and I can get a very accurate GPS lock in about three seconds, without the 'fix'. I havent noticed a single problem with the phone. The only thing I have a question about is this 5.1 Channel Surround Sound. It says you can only use it in headphone mode-but when I put in the headphones that came with the Vibrant the only thing I notice is it makes the movie/music higher pitched. Is that all it does or am I missing something?
Click to expand...
Click to collapse
Mine was the same way until I rooted it.
After I rooted it I went from 18 hour battery life to 6-8 and the freezing problem got really really bad, the more apps I put on the phone the worse it got, it got to the point were I got a black screen for 3-5 minutes every other app I opened.
My GPS also worked perfectly but I try the 1st "fix" and I had nothing but problem ever sense I did it.
I returned mine for a new one and everything worked great except the GPS and I applied the 2nd fix and all works great now.
Moral of the story is
If it's not broke don't fix it
I'm not going to root my phone until things are ironed out.
siberslug said:
Mine was the same way until I rooted it.
After I rooted it I went from 18 hour battery life to 6-8 and the freezing problem got really really bad, the more apps I put on the phone the worse it got, it got to the point were I got a black screen for 3-5 minutes every other app I opened.
My GPS also worked perfectly but I try the 1st "fix" and I had nothing but problem ever sense I did it.
I returned mine for a new one and everything worked great except the GPS and I applied the 2nd fix and all works great now.
Moral of the story is
If it's not broke don't fix it
I'm not going to root my phone until things are ironed out.
Click to expand...
Click to collapse
I loved reading what uninformed users think. The Update.zip only installs Superuser.apk, SU, and Busybox. All three only run when called upon by another application, and then exit. You battery issues are unrelated, more than likely caused by leaving your brightness up too high, or wifi or bluetooth on. The lag is a known issue by Samsung. It is caused by the way app data is stored, and can be remedied by moving the datadb to another partition and sym-linking. Blaming these problems on rooting is like blaming a flat tire on the oil change you got last week, it's just ignorant and uninformed.
Also, all of this is unrelated to the original post, so please, stop trying to thread jack and take your misinformed opinion elsewhere.
siberslug said:
Mine was the same way until I rooted it.
After I rooted it I went from 18 hour battery life to 6-8 and the freezing problem got really really bad, the more apps I put on the phone the worse it got, it got to the point were I got a black screen for 3-5 minutes every other app I opened.
My GPS also worked perfectly but I try the 1st "fix" and I had nothing but problem ever sense I did it.
I returned mine for a new one and everything worked great except the GPS and I applied the 2nd fix and all works great now.
Moral of the story is
If it's not broke don't fix it
I'm not going to root my phone until things are ironed out.
Click to expand...
Click to collapse
Well, I don't know how rooting cause all that, 'cause all rooting the vibrant consists of is copying Superuser.apk, su and busybox over.
Zing!
That was a bit harsh.
I've been having this issue with my epic for the past month or so. If something (other than a phone call) is playing audio (game, music) through the speaker or the earbuds I hear a crackling noise when I touch the screen and only when I touch the screen. It's very easily reproduced too. For example, I'll have pandora playing through the speaker and it'll play fine until I touch the screen to change the song or do something else. If I keep my finger on the screen it'll continue making the crackling noise until I lift it off. Doesn't happen if I touch the screen while it's off. The same thing has happened on every rom I tried including odin to stock eb13 and ec05. Since I've had the phone for less than a year, can I take it to a sprint store and get a replacement? Or does anyone have any idea how to fix this?
Sent from my SPH-D700 using XDA App
This may not make the most sense, but it sounds like you've got some exposed wires or something on the inside, my guess would be that the capacitive touch screen is causing some feed back when the field is broken and you touch it. May be a bad capacitor, or just some crossed/exposed wire, but we have had a similar issue with a wall touchpad in one of our class rooms. they control a Audio visual box and once it was damaged would produce a crackling over the speaker system when you would use the touch pad to change source or adjust volume and the AV box was turned on. The unit had to be replaced, I'd be willing to bet the same would go for the phone as replacement parts wouldn't be the easiest to come by.
gearless said:
This may not make the most sense, but it sounds like you've got some exposed wires or something on the inside, my guess would be that the capacitive touch screen is causing some feed back when the field is broken and you touch it. May be a bad capacitor, or just some crossed/exposed wire, but we have had a similar issue with a wall touchpad in one of our class rooms. they control a Audio visual box and once it was damaged would produce a crackling over the speaker system when you would use the touch pad to change source or adjust volume and the AV box was turned on. The unit had to be replaced, I'd be willing to bet the same would go for the phone as replacement parts wouldn't be the easiest to come by.
Click to expand...
Click to collapse
Do you think I should call Sprint first or just go into a store?
dieselg5 said:
Do you think I should call Sprint first or just go into a store?
Click to expand...
Click to collapse
Go into the store so they can see the problem personally. They will most likely order you a refurb.
dieselg5 said:
Do you think I should call Sprint first or just go into a store?
Click to expand...
Click to collapse
Go to a store, Sprint will tell you that over the phone. haha
This is a well known issue around here. Hold up ill dig up a post about it. I am happy to say that as of Bonsai 4.1.1 this issue no longer exists.
http://forum.xda-developers.com/showthread.php?t=1026971
dieselg5 said:
I've been having this issue with my epic for the past month or so. If something (other than a phone call) is playing audio (game, music) through the speaker or the earbuds I hear a crackling noise when I touch the screen and only when I touch the screen. It's very easily reproduced too. For example, I'll have pandora playing through the speaker and it'll play fine until I touch the screen to change the song or do something else. If I keep my finger on the screen it'll continue making the crackling noise until I lift it off. Doesn't happen if I touch the screen while it's off. The same thing has happened on every rom I tried including odin to stock eb13 and ec05. Since I've had the phone for less than a year, can I take it to a sprint store and get a replacement? Or does anyone have any idea how to fix this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
p3dr0maz said:
This is a well known issue around here. Hold up ill dig up a post about it. I am happy to say that as of Bonsai 4.1.1 this issue no longer exists.
Click to expand...
Click to collapse
Must be various on a per phone basis then, because I've flashed EVERY single ROM to date and I've never experienced that.
p3dr0maz said:
This is a well known issue around here. Hold up ill dig up a post about it. I am happy to say that as of Bonsai 4.1.1 this issue no longer exists.
http://forum.xda-developers.com/showthread.php?t=1026971
Click to expand...
Click to collapse
It doesn't sound like a software issue, therefor a rom won't fix the issue. If he goes back to stock, and the issue persists its hardware. Sounds like a loose wire, but I can't be sure...
Sent from my SPH-D700 using XDA Premium App
XtaC318 said:
It doesn't sound like a software issue, therefor a rom won't fix the issue. If he goes back to stock, and the issue persists its hardware. Sounds like a loose wire, but I can't be sure...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
We were trying to track down the cause, but never did, we still think it might be vodoo sound related when its built into the kernel...
But if it happens on stock, it could be something else, only happens to me on modded kernels.
If you can see this link please take a few moments to click and read, its for a good cause, you can make a difference, help spread the word today...
http://www.picketfenceblogs.com/vote/3616
I've never expiernced this either
Not sure what to say if it happens on stock. Proud to say i've never ran stock except for the 2 minutes before I flashed a custom ROM. And yeah I mentioned the ROM because it does have a custom kernel and even though we've all heard arguments that it's this or that i still have to say it's gotta be something in how voodoo is compiled into the kernel like ecooce says.
So I odin back to DI18 and let it update before I took it to the store and of course it's not happening anymore
I remember going back to stock after ACS 1.1 destroyed my phone a few times (my phone would freeze a lot and since there's no journaling in 1.1 everything would get corrupt) and I still had the issue. Playing air attack hd with the crackling was horrendous. Anyway, thanks for the support everyone. Sorry for the scare
dieselg5 said:
I've been having this issue with my epic for the past month or so. If something (other than a phone call) is playing audio (game, music) through the speaker or the earbuds I hear a crackling noise when I touch the screen and only when I touch the screen. It's very easily reproduced too. For example, I'll have pandora playing through the speaker and it'll play fine until I touch the screen to change the song or do something else. If I keep my finger on the screen it'll continue making the crackling noise until I lift it off. Doesn't happen if I touch the screen while it's off. The same thing has happened on every rom I tried including odin to stock eb13 and ec05. Since I've had the phone for less than a year, can I take it to a sprint store and get a replacement? Or does anyone have any idea how to fix this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I am glad you fixed it.
Kernel bug. Likely not a hardware issue.
I have the same exact behavior with Genocide 1.0. I'm unaware if this occurs in other Voodoo sound enabled Kernels but it sounds like it does.
On stock EC05 the problem goes away. For me anyways.
It does for most. TWZ 1.4 doesnt have the problem and neither does Bonsai 4.1.1 kernel AFAIK. There might be other known good combos.
TheDub said:
Kernel bug. Likely not a hardware issue.
I have the same exact behavior with Genocide 1.0. I'm unaware if this occurs in other Voodoo sound enabled Kernels but it sounds like it does.
On stock EC05 the problem goes away. For me anyways.
Click to expand...
Click to collapse
I have the same issue on certain kernels. I was just about to ask, too. VERY noticeable when I'm playing music in my car and need to do something onscreen, makes the audio sound terrible.
I had this issue on several roms, including acs and the previous bonsai. In fact, my experience with acs was identical to yours. My phone just didn't play well with it. I don't have this problem with stock plus rom, even with the genocide kernel. Give that one a shot.
Sent from my SPH-D700 using XDA App
greezestain said:
I had this issue on several roms, including acs and the previous bonsai. In fact, my experience with acs was identical to yours. My phone just didn't play well with it. I don't have this problem with stock plus rom, even with the genocide kernel. Give that one a shot.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
or its loose wire on your audio jack could be short to graounf when you tap the phone
TheDub said:
Kernel bug. Likely not a hardware issue.
I have the same exact behavior with Genocide 1.0. I'm unaware if this occurs in other Voodoo sound enabled Kernels but it sounds like it does.
On stock EC05 the problem goes away. For me anyways.
Click to expand...
Click to collapse
Mine also crackles when the brightness adjusts. This includes when the screen fades out when I turn it off.
I hadn't noticed it when simply touching the screen though, just with the brightness. Also, I never noticed it until I started running custom roms with voodoo built in.
Sent from a secret underground bunker
Download voodoo control and turn down headphone amplifier or turn down volume limit. Might do the trick.......
Well as I found out when my SD card died it also took out my GPS, nothing will make it work again. So I put the phone back to stock, got the ED03 Froyo OTA update and took it into my verizon store, long story short I'm getting another phone tomorrow. I've been rocking on the stock froyo for a few days now and its kinda wierd since I've basically been rooted from day one. For one battery life is horrible with anything turned on, however with everything toggled off my battery life is alot better than any custom ROM or undervolted kernel. I didnt expect that. Phone isnt as laggy and i expected either. Whats really bizarre is when your stock the Market actually WORKS! No matter what I flashed my Market was always laggy, sometimes never worked at all. I usually have to start a download two or three times. This was for any ROM or kernel I tried, I assumed it was normal. Well on stock Froyo, the Market loads immediately, when I click to dowload it downloads and installs immediately. WOW! Now when I get my new phone I'm gona root it , is there anyway to get this good Market performance?
I don't have any market issues on comrom 1.3
My phone performs much better on stock ED03 than Community ROM v1.3. Is there a lot more broken with that ROM than the kernel & status bar?
For the past few days I've also been running stock ED03 with the basic bloat removed and minimal apps installed. Battery life is a bit better, but it's still not great. The phone is typically dead (or screaming for a charger) by the end of the day with normal use.
Everything seems to work with the exception of bluetooth calling (after I hang up) in my car. At first I thought it was those custom kernels causing the issue, but even the stock kernel/ROM does it.
After I hang up a call via bluetooth in my car, the phone crashes and bluetooth crashes which makes the phone hang for a minute or two. I can turn bluetooth off then on to get it to re-connect to the car, but it'll just crash again after the next call is done. Through some reading, I found that Samsung is real shady with their implementation of bluetooth. I can believe it based on our GPS issues, jacked up RIL code, weak wi-fi signal and a lower overall cell signal than other phones.
It's **** like this that keeps me from wanting the SGS II.
I'm out of the loop but it seems as it stands LG is the way to go
AuroEdge said:
I'm out of the loop but it seems as it stands LG is the way to go
Click to expand...
Click to collapse
I don't know I just played with a htc thunderbolt yesterday at a verizon store and that thing is bad ass even without 4g. If us cellular got that phone id be all over it. But from what I hear we getting the moto atrix which I'm not a huge fan of...now that moto xoom tablet on the other hand...if verizon wasn't so damn expensive.... My $.02 haha
As for the stock experience I just flashed back from cm7 to stock and all I got was pissed off haha
Sent from my SCH-I500 using XDA Premium App
ive had issues with the market in custom roms too. sometimes when i download an app instead of installing it just disappears, and i have to redownload it sometimes more than once to get it to install. but that wont make me go back to stock. custom roms/kernels are waaay better than stock and theres bound to be some issues here and there
AuroEdge said:
I'm out of the loop but it seems as it stands LG is the way to go
Click to expand...
Click to collapse
I had the LG G2x for a little over a week and it wasn't too bad. There were very minor annoying things (which I cannot remember) that reminded me of Samsung, but it wasn't as bad. It was supposed to be stock Android, but a developer soon discovered that it wasn't. It was just themed to appear stock, so I don't think the G2x currently performs as good as say a Cyanogen ROM.
Also, that phone was plagued with that reboot bug. Outside of the reboot bug and the LCD screen, it's not a bad phone. I couldn't keep it because A) the software bugs reminded me of why I don't want another Samsung. I'm not going to buy a phone and put up with that BS again - although, that phone should get heavy dev support soon; B) Maybe it was the 4" screen or the bottom heavy bezel or the bleeding LCD screen, but I felt the phone was too much of a lateral step rather than a step up from the SGS series of phones. I needed more to keep myself satisfied.
LG has the potential to do good, but so far... they're on shaky ground to me. Just like Samsung. They need to fix the reboot issues and stop copying Samsung.
As it stands I will stick it out with my Fascinate till I see a Verizon phone I really like. Which sucks because I don't see any on the horizon that look promising except for maybe the Motorola Targa. When it comes to community efforts there are two reasons I look to them from time to time -- stability and believe it or not BLN
Beware of the LG Revolution when it drops. It's not going to be a "With Google" device, meaning Verizon is probably going to beat and rape it until it's a mere shadow of it's original self.
Running stock ED03, rooted, modified to support cwr, de-binged, de-bloated, and deodexed. I did this all myself, a lot of reading of how to's. Next up I found something on converting rfs to ext4 I hope it easy enough and works well. So far its great, with the prospect of awesome, if file extention Change is doable and improves phone as much as I read about.
Sent from my SCH-I500 using XDA Premium App
First of all, I know that I have read about this problem in other threads but I cannot find it; I think it was associated with custom ROMs but I'm not entirely sure.
I have two problems with my sound right now:
popping
Every time the tables boots up the speakers pop. No a big deal and it might be just because they get activated and the current causes the pop. But every time a sound is made? That is annoying!
humming/screeching/buzzing
Now this is the scariest problem. The sound that comes from "within" the tablet, i.e. behind the screen and not the actual speakers. It does not always appear but seems to be linked to apps trying to use sound. It almost sounds like a hard drive spinning irregularly or a distant old dial-up modem (weird analogy, I know). I don't know what's causing it but in my opinion it's not a good sign.
Again, if anyone here remembers where it has been discussed already I will take the blow as long as I can find out if the problem(s) have been solved somewhere.
Thanks y'all!
1. Everyone's device does that. It's just the way the device wakes the speakers before playing a sound as you say. Would hope Asus could do something about that in the future.
2. It sounds like you are hearing the screen's backlight frequency. Not everyone will hear this (as we lose the ability to hear certain frequencies as we get older), but again it happens with everyones device, and is normal with any screen using a backlight.
Do you have a custom rom on it?
Oyeve said:
Do you have a custom rom on it?
Click to expand...
Click to collapse
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
stuntdouble said:
2. It sounds like you are hearing the screen's backlight frequency. Not everyone will hear this (as we lose the ability to hear certain frequencies as we get older), but again it happens with everyones device, and is normal with any screen using a backlight.
Click to expand...
Click to collapse
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Process of elimination.
Roll back to stock and see if the problem occurs. If so, sounds like you’re going to have to return it for an exchange.
smellmyfingers said:
Process of elimination.
Roll back to stock and see if the problem occurs. If so, sounds like you’re going to have to return it for an exchange.
Click to expand...
Click to collapse
The scientific way, I like your idea
Do you also know if there has been a use for the SBK to enable root for the stock ROM?
funnycreature said:
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Click to expand...
Click to collapse
Each app will tell your device to process the images onscreen in different ways, whether thats the refresh rate, resolution or just pixel density, so you would still get different frequencies from different apps all the time. Anyway I'm not saying that's 100% the reason, it's just a possibilty based on what you were describing.
stuntdouble said:
Each app will tell your device to process the images onscreen in different ways, whether thats the refresh rate, resolution or just pixel density, so you would still get different frequencies from different apps all the time. Anyway I'm not saying that's 100% the reason, it's just a possibilty based on what you were describing.
Click to expand...
Click to collapse
Very good points! Never thought of it this way... Do you also think it's worth going back to stock and try to figure it all out or just take it "as is"?
If it is what I thought it was, it won't make a difference which rom you use, and it's a normal feature of the tablet. You must live in a very quiet place to hear it all the time or have very sensitive ears. If it's not that, then trying another rom as mentioned above may help you narrow down the list of causes. If it's annoying you too much then possibly it IS a fault with the tablet and in which case you'd need to get a replacement. If it was me I'd probably roll back to the stock rom just to see.
stuntdouble said:
If it is what I thought it was, it won't make a difference which rom you use, and it's a normal feature of the tablet. You must live in a very quiet place to hear it all the time or have very sensitive ears. If it's not that, then trying another rom as mentioned above may help you narrow down the list of causes. If it's annoying you too much then possibly it IS a fault with the tablet and in which case you'd need to get a replacement. If it was me I'd probably roll back to the stock rom just to see.
Click to expand...
Click to collapse
After 20 years of listening to metal I highly doubt that my ears are that sensitive but you never know I might try the stock ROM as soon as it has been rooted but for now I don't think it's worth it. I was more worried about something inside the device being tortured
funnycreature said:
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
Click to expand...
Click to collapse
I hear the buzzing sound too and I am also unning Prime 1.4 ROM and Clemsyn-Blades KERNEL. I hear it on the Left side of the tablet and sounds like its coming from the speaker but more towards the screen edge. Never heard it on Stock though.
dja2k
I'll have to wait for another reboot to test this, but I hear what I call high pitched 'tweeting' from the speaker I just have to touch the volume up/down button on the tablet and it seems to instantly stop.
I'll test here in a bit. Using Primordial 3.1 and the OC Kernel at 1.4 right now.
Update: 'twas my imagination on the touching of the volume button. It squeals a bit thru all the ASCII art and status boot screens, but settles down when the lock screen appears. Not a nuisance, but audible.
Sent from my Transformer TF101 using XDA Premium App
I updated the Clemsyn-Blades v6 KERNEL to v7ELITE and I don't hear the buzzing sound anymore. Maybe it was that version of the custom KERNEL. I will check it out, maybe it is just random.
dja2k
funnycreature said:
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Click to expand...
Click to collapse
It's the custom kernel you're using, mine was doing the same thing with some weird high pictched sounds too. I reflashed the stock ASUS kernel and it hasent done it since. Just to make sure, I reflashed the custom kernel you're using and the speakers make the humming noise again.
cdpriest said:
It's the custom kernel you're using, mine was doing the same thing with some weird high pictched sounds too. I reflashed the stock ASUS kernel and it hasent done it since. Just to make sure, I reflashed the custom kernel you're using and the speakers make the humming noise again.
Click to expand...
Click to collapse
I haven't noticed the humming since v7 of Clemsyn/Blades' kernel. But the popping is as bad as ever. I wish there was a fix for that too!
funnycreature said:
First of all, I know that I have read about this problem in other threads but I cannot find it; I think it was associated with custom ROMs but I'm not entirely sure.
I have two problems with my sound right now:
popping
Every time the tables boots up the speakers pop. No a big deal and it might be just because they get activated and the current causes the pop. But every time a sound is made? That is annoying!
humming/screeching/buzzing
Now this is the scariest problem. The sound that comes from "within" the tablet, i.e. behind the screen and not the actual speakers. It does not always appear but seems to be linked to apps trying to use sound. It almost sounds like a hard drive spinning irregularly or a distant old dial-up modem (weird analogy, I know). I don't know what's causing it but in my opinion it's not a good sign.
Again, if anyone here remembers where it has been discussed already I will take the blow as long as I can find out if the problem(s) have been solved somewhere.
Thanks y'all!
Click to expand...
Click to collapse
Sound like you got a Bee in there eathing rice crispies
I have been using Android since cupcake and it's going to end with my Nexus One. Reasons:
These are problems I've had with various roms, most stock roms, some MIUI:
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
- My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
- To fix the above I got Better Keyboard. It force closes often, and sometimes when I try to type with it what I'm typing doesn't get inserted into the selected input box.
- I got five hours of STANDBY (not using phone at all) battery life on Gingerbread. I had to downgrade back to froyo to get normal battery life back.
- After ten seconds or so if you don't use your screen it's supposed to DIM. Regardless of whether or not I'm using my phone it still dims after ten seconds.
So as far as Android goes come October when my three year Bell contract expires I'll be selecting an iPhone. I am done with Android problems of all kinds. That's not to say there's not a lot of things I like about Android but I can't just keep on going with it whilst experiencing these annoying problems, when I've never experienced any problems of any sort on my jailbroken iPad.
Did you ever try using your warranty? Really sounds like you had a dodgy handset.
Sounds like your phone is a lemon. I experience none of that....don't think anything you mentioned is a problem of android itself, you just got unlucky with your phone
Sent from my Nexus One using XDA App
Sounds like some bad flashing you been doing to your phone
Sent from my Nexus One using XDA App
lemons
.
You must be holding it wrong, those are some crazy problems you are experiencing ... I've never had any of those.
Macmee said:
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
Click to expand...
Click to collapse
Not related to Android in the slightest. You're having a HARDWARE problem.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
Click to expand...
Click to collapse
Not related to Android in the slightest. You're having a HARDWARE problem.
My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
Click to expand...
Click to collapse
In all of my time with Android, on multiple devices, I have NEVER once seen this issue. Something is wrong with the custom rom you're running... which btw, YOU flashed on your phone.
To fix the above I got Better Keyboard. It force closes often, and sometimes when I try to type with it what I'm typing doesn't get inserted into the selected input box.
Click to expand...
Click to collapse
So some janky app YOU installed is causing a problem? Uninstall it and find something better.
I got five hours of STANDBY (not using phone at all) battery life on Gingerbread. I had to downgrade back to froyo to get normal battery life back.
Click to expand...
Click to collapse
Did you try and diagnose this at all? Were you having a wake lock issue? Was some app freezing?
I go all day on Gingerbread, especially if I don't even use it...
After ten seconds or so if you don't use your screen it's supposed to DIM. Regardless of whether or not I'm using my phone it still dims after ten seconds.
Click to expand...
Click to collapse
Again, this sounds like either something wrong with your rom or a hardware issue. I have never seen this issue.
Yeah, you're an idiot. Sorry, but you're blaming problems that either you have created or hardware problems on Android, the operating system.
But go ahead and leave Android. It sounds like you're not really technology capable of much more than an iPhone (and really, this is probably going to be pushing your technological limits it seems), so that is probably what you should stick to.
I won't be as harsh as the others
The only problem you mentioned that is N1 related is the screen, rest are probably rom related. If your flahsing all those roms you already know they are not guaranteed to work on all phones.
If you want to try another phone, try the new Sensation or equivalent. Android is still much better than Apple. IMHO. That said, my son and his wife have been Apple users for 20 years or as long as I can remember. They have used nothing else. So, I think the iphone is a good phone, just not for everyone. As android is not for everyone. I once thought Blackberry was unbeatable, I was wrong bigtime. When I first started using them, they may have been. But, not any more.
You are probably like me and get an itch to try something different. I am currently running RCADSmix Sense rom with a number of issues. But, I like it so much, I will put up with the issues. Probably means my next phone will be the Sensation or it's future quadcore brother.
Enjoy whatever you get, I still remember when a six transistor am radio was an upgrade. These are great tech times--
Ken
If you really can't realize that the problems you are experiencing are hardware related...it's probably better you get an iphone. Bye and don't let the door hit you on the way out
So as far as Android goes come October when my three year Bell contract expires I'll be selecting an iPhone. I am done with Android problems of all kinds. That's not to say there's not a lot of things I like about Android but I can't just keep on going with it whilst experiencing these annoying problems, when I've never experienced any problems of any sort on my jailbroken iPad.
Click to expand...
Click to collapse
Im just guessing here but your in Canada with bell? bell doesn't offer the nexus one. how are you on a contract? Ill also agree with everyone else your problems are not android related. Sounds like a hardware issue. Good luck with the iPhone my brother loves his. I like the design but that's it.
Just flashed cyanogen latest version. New problems:
1. Sometimes when turning on the phone the lock screen doesn't show up, just my background displays and nothing else. Reboot required by pulling battery out in order to fix.
2. Display menus don't show up sometimes.
3. Already experienced this one, but the keyboard is yet again going completely white.
Anyone want to point me towards an actual working rom without any problems or does such a thing exist
wsrider said:
Im just guessing here but your in Canada with bell? bell doesn't offer the nexus one. how are you on a contract? Ill also agree with everyone else your problems are not android related. Sounds like a hardware issue. Good luck with the iPhone my brother loves his. I like the design but that's it.
Click to expand...
Click to collapse
I bought it outright two years into my contract when I had a vogue.
Babydoll25 said:
If you really can't realize that the problems you are experiencing are hardware related...it's probably better you get an iphone. Bye and don't let the door hit you on the way out
Click to expand...
Click to collapse
Because not all of these problems are with the hardware and you, or myself are incapable of diagnosing them without more extensive investigation to the handset.
Roms work fine. Your phone doesn't
Most people have no or little problems with these roms
Most if not all issues are improper flashing or incomplete wipes--like not wiping system and data and caches multiple times
Check md5s
Or, not properly partitioning sdcard
If still issues then the phone has too many bad blocks for the rom and kernal
Ken
After reading your first post again, I think it is your phone and not common issues. I have never had a bad camera unless specifically noted on the OP page of an alpha type rom.
I can tell you how I do my sdcard and prepare for a new rom if you like. If my procedure doesn't work you will never have any better luck flashing with that particular phone.
Sorry
Ken
I'm with Telus on my N1 and i've never ever seen any of the problems you mentioned. I've also flashed alot of different roms/kernels/apps/etc and nothing like you had mentioned.
I did however have an issue that resembles your camera issue. Mine was the GPS causing my phone to reboot every time i used it. I didn't really notice it much until i started using it for GPS nav and such. Tried flashing different roms, going back to stock and issue still came up. Called HTC and sent my phone back under warranty. They told me they replaced the board and i have not seen the problem ever since.
I strongly recommend giving HTC a call and see if you can send your phone in for repairs.
That's what iPhone is for. To protect incompetents like yourself from themselves.
You should be nowhere near a rooted phone.
I have the exact same camera issue. The reason is a date of my beloved Nexus and my washing mashine. So it might be a hardware problem for you as well. Sometimes with some roms the camera seems to work 1 out of 10 times.
Bluetooth, fm radio died as well but everthing else is just fine. Some roms seem to check/use camera, radio or bluetooth during a reboot. Then the rom won't start at all or it makes random problems.
This phone is a beast. 20 minutes in the washing mashine at 60°C couldn't really destroy it. Even between screen and digitizer there was water and I had to disamble the phone three times and dry the parts for one week in a rice bowl to get it to work again.
xManMythLegend said:
That's what iPhone is for. To protect incompetents like yourself from themselves.
You should be nowhere near a rooted phone.
Click to expand...
Click to collapse
+1
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
- My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
Click to expand...
Click to collapse
Got this also, annoying but I'm quite sure it goes along with flashes. Pretty sure it will be normal on stock rom.
Actually mate I think you should upgrade your radio...
I used to have this issue with the camera before, get the latest radio and ur camera issue will be solved.
and the battery as well i guess
as for the keyboard and all the other problems just go to rom manager and flash cm 7.1 rc1 from there, make sure you wipe cache, and dalvik cache
it should solve ur issues
Android is a more technical platform, it is by default that the user likes going technical before getting an android