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
Related
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.......
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
So I tend to answer more questions that I ask on here, but now it's my turn!!
So, I've noticed at times that my KF is totally unresponsive from sleep. No power light, nothing. I have to press the power button for 20 seconds, then again to power on. This used to happen every so often on the Stock ROM.
However, since I've been on CM7 w/ TWRP/FFF, it hangs up every single day. At first I thought it was due to low charge, but it's doing it whilst the battery is over 90% full. I've had a nose around the CM7 settings and tweaks, but can't see anything obvious.
Running services at startup are:
Settings (presumably because I'm looking at settings to see this info!)
Google Services
Amazon Video (Not sure why this is running. I may uninstall to see if this is the problem) - Uninstalled. Will see how it goes.
DSPManager
Swype
Anybody else seen this? Anybody else got any ideas on how to resolve this?
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
I've not experienced this problem. My kindle fire has been pretty much perfect and I've never had to force a reboot. I'm also using the Sywpe keyboard.
asb2164 said:
Do a search for V6 SuperCharger and do some research on it I use it on my Fire and my 2 Android Phones it really helps with memory management
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
sl0ttedpig said:
Thanks, but I don't think memory is the problem here (I have 282MB free system memory right now). Something is putting it to sleep permanently.
I guess it's going to be a process of elimination. I might possibly go back to stock to see if it's really CM7 or the device hardware itself playing up.
Click to expand...
Click to collapse
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
asb2164 said:
I would not even bother reading the information I provided, reading is pretty hard chase a lot of gremlins first instead of the running a Script.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Wow, seriously?!
I *did* read about it, and concluded that it was a memory management app. Given my symptoms, I cannot find one example of where this app would help me, and I'm not about to install something that is possibly just going to add further variables to an already odd behavior.
Show me where you think it's going to help (specific examples), and I'll gladly accept your thanks/suggestions.
Until then, I would ask you keep your snark for sites like Slashdot.
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
asb2164 said:
You did not read about it if you had you would have known it is not an app but a Script.
I do not hold people's hand and give links I make you search for it I am sure someone will come along and make you a video
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Again, Wow Seriously?!
Your definition of me not reading is based on me calling it an app over a script!? Interesting logic there.
However, I'm still wondering how you deduce that this is going to help my problem, and hence why I asked for specifics. I'm quite capable of finding information, but it's like you saying to me "Dude, install Angry Birds, it will solve all your problems". My conclusion was that there was nothing in that post that specifies "This will also help your system if it sleeps permanently" (clearly I'm paraphrasing there, just in case that wasn't clear). If I'm missing something, I'm all ears, but blindly recommending apps for no reason is no help to anyone.
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
asb2164 said:
Other than almost every decent ROM you will find on XDA already has this built into it and it will help I will leave it at that.
You also may try to wipe Data, Cache and Dalvik I usually do that at least 3 times on my HTC EVO Shift when I flash a new rom before it runs good.
Try that and see if it helps.
Click to expand...
Click to collapse
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
asb2164 said:
You may have a bad flash back up your apps and re-flash CM7 and restore your apps and see if that helps.
I have rooted and flashed a lot of phones and I have had that happen a couple of times I re did the flash and everything was fine.
Click to expand...
Click to collapse
I guess it's entirely possible. I'll do a Titanium Backup now, re-flash, and see what happens. But as mentioned in my OP, I had this happen on stock 6.2, just not as frequently, so I'll be hoping that it is a bad flash, and not something inherently worse.
See how much better this conversation is now!
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Your problem is a bit unique so I don't mind throwing out a few ideas.
Mine is solid as a rock I am ready for a good overclocking kernel so I can stretch it's legs
Sent from my Kindle Fire using Tapatalk
altitude909 said:
Sounds fishy to me as well. Did you clear the caches when installing new ROMs? I've had mine since it was release and have yet to have it hang and I've had 6.1,6.2, and now CM7 running flawlessly
Click to expand...
Click to collapse
Yep, I always clear everything when moving to a new ROM. It's a habit that was drilled into me during my first custom ROM exploits on my Droid. I've even told people on here to do it too, so I'm practicing what I'm preaching!
I think what I'm going to do is, reflash to stock 6.2.1, use the new root method, push TWRP/FFF again, and then CM7. A little drastic, but I think that having a clean run at this might prove/disprove the theory.
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
krelvinaz said:
My stock rom does this occasionally. Have to hold the power button for 20 secs to reset it.
Click to expand...
Click to collapse
Yeah, this is happening a little too frequently for my liking. Occasionally is fairly OK, every day is not. But it has got worse since going to CM7, but that could be purely coincidence at this point.
Trying some different things right now, but it will be a few days before I know for certain.
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
butterflygirl said:
This may not be the problem at all, but I'll toss it out here anyway. On some of my Archos tablets, I have had this issue where the screen brightness was set very low. Anyway, if your brightness is set low, you might increase it to see if that makes a difference. I don't remember exactly at what level this problem starts, but I think it is when it is set below 20%.
Click to expand...
Click to collapse
Thanks, that hadn't crossed my mind, but I like my brightness at a pretty high level, and as the sensor is not working currently, it pretty much stays at that level.
Back at stock 6.2.1 now. Going to root it and leave it like this for a few days to see what happens.
sl0ttedpig said:
It may well be the CM7 ROM that was compiled for the KF, but what also makes me suspicious now is for the number of reads on this thread, not one other person has said "Yeah, I have the same issues", which either leads me to believe its a resident app, or possibly something wrong with my hardware. I'll keep digging, and possibly flash back to stock (as I said).
For the benefit of doubt, I'll always do a Factory Reset, and wipe all the Cache/Dalvik Cache. It's something I've done since I was flashing ROM's on my first Droid. But thanks for the suggestion.
Click to expand...
Click to collapse
Not sure if you have resloved this issue, but having read most of the Forum Dev Thread for the CM7 initial release and the newest reboot of the first ROM I think many others are having this issue as well. I remember reading many post people were referring to something similar to your problem as "the sleep of death." I however am not having that problem with mine, but thought it might be helpful to know that it might not be your device specific and may be something with CM7 itself with some devices.
I'm sure this happens to most if not all Nexus 4 phone, but either it doesn't disturb the owners or most owners never notice it (or notice it but don't bother to think more of it.). I'm a sound person in general so it kind of annoys me.
This issue occurs usually when you haven't picked up your phone in a few minutes (or any amount of time more than a few minutes maybe) and you interact with it. The first time the phone tries to generate a sound (a touch or keyboard click sound maybe?) you might hear some kind of a very short pop/click noise just a little bit before you hear your normal sound. Then the rest of the sounds go on as they should, until you leave your phone aside and pick it up later again.
So, I actually wonder if anyone has bothered with that and if any talented developers have considered looking into it but abandoned hope. There's a case this could be hardware but I can't tell. Maybe someone can make a hack so that when the sound system wakes up when invoking a sound it performs some sort of fade-in first.
Anyway, I think this is an interesting issue and I'd love to hear what you think.
kokotron said:
I'm sure this happens to most if not all Nexus 4 phone, but either it doesn't disturb the owners or most owners never notice it (or notice it but don't bother to think more of it.). I'm a sound person in general so it kind of annoys me.
This issue occurs usually when you haven't picked up your phone in a few minutes (or any amount of time more than a few minutes maybe) and you interact with it. The first time the phone tries to generate a sound (a touch or keyboard click sound maybe?) you might hear some kind of a very short pop/click noise just a little bit before you hear your normal sound. Then the rest of the sounds go on as they should, until you leave your phone aside and pick it up later again.
So, I actually wonder if anyone has bothered with that and if any talented developers have considered looking into it but abandoned hope. There's a case this could be hardware but I can't tell. Maybe someone can make a hack so that when the sound system wakes up when invoking a sound it performs some sort of fade-in first.
Anyway, I think this is an interesting issue and I'd love to hear what you think.
Click to expand...
Click to collapse
Mine doesn't have this issue.
xda6969 said:
Mine doesn't have this issue.
Click to expand...
Click to collapse
Interesting, can you tell me if you are on stock or a different rom (or different kernel or whatever) ?
kokotron said:
Interesting, can you tell me if you are on stock or a different rom (or different kernel or whatever) ?
Click to expand...
Click to collapse
I'm running everything stock.
xda6969 said:
I'm running everything stock.
Click to expand...
Click to collapse
Replies I got at G+ indicate that this is a hardware issue and that indeed it has been around. And that I should go for a replacement. Bollocks.
Easy to test, go to a very quiet room. Really quiet. Put your phone to your ear while screen off and listen. (Not phone off)
You will hear a faint sound, static, cracking well some kind of noise.
This is nothing new, and not just bound to this phone. However I had this issues only on the Nexus 4 and never noticed it on other phones I had.
It becomes a bit annoying while in call, really quiet room, and every pause, when both parties are not talking.
I think only option is learn to live with it? As if the numerous threads from N4 and other devices are true, this is a HW fault on all devices. Some ppl just do not hear it. What varies is the intensity, which ppl reported that exchanged their devices.
Is there someone on some variant not hearing it? (State your age as well)
Is there someone who exchanged their device based on this problem and got a new one with a different level of the noise?
Mine is international LG D802
I do hear the pops and squeals when I'm on a call, but not otherwise. VZW version, rooted, stock rom, "A" version of modem/radio.
Here's the thread I started: http://forum.xda-developers.com/showthread.php?t=2502265
rfarrah said:
I do hear the pops and squeals when I'm on a call, but not otherwise. VZW version, rooted, stock rom, "A" version of modem/radio.
Here's the thread I started: http://forum.xda-developers.com/showthread.php?t=2502265
Click to expand...
Click to collapse
The sound that you experience, since its through your BT as well, might be normal connection/call sounds. I have this really on all phones even sometimes on iPhone. But if its something tha tyou do not expect to hear, and have it constantly , bring it for repairs, I do not have somehting out of the ordinary in the calls, except what I described in the OP.
What I mean its really like static electricity, cracking sounds. But its faint, you won't notice it in normal environment, at least not when you do not know what to look for. There are youtube videos for the N4 with the sound I mean. cant listen to it now, as I am at work but I think something like this http://www.youtube.com/watch?v=9wOxtzStUZ4
you really need a quiet environment, put your ear to the earpiece.
Also thanks for your post!
I am on ATT and noticed this and I was thinking about returning it but I tested the display model at the ATT store and the same thing. I tested an Iphone 4s and the same thing with the earpiece. I think this is more common than people think because you really have to be in a quiet setting to actually hear it. Thanks
z45123 said:
I am on ATT and noticed this and I was thinking about returning it but I tested the display model at the ATT store and the same thing. I tested an Iphone 4s and the same thing with the earpiece. I think this is more common than people think because you really have to be in a quiet setting to actually hear it. Thanks
Click to expand...
Click to collapse
FWIW, I haven't had this issue at all since the update came out months ago. Maybe they just haven't updated the demo model in the store.
Thanks for the info are you saying you had the issue prior to KitKat and the OTA with KitKat resolved the problem
z45123 said:
Thanks for the info are you saying you had the issue prior to KitKat and the OTA with KitKat resolved the problem
Click to expand...
Click to collapse
Nope, had the issue before VZW did their radio update. No KK update for us yet.
Im on att and wish there was some sort of software patch for this
I have the same issue (internationl LG G2)
Isn't there any fix?
Mr.Kos said:
I have the same issue (internationl LG G2)
Isn't there any fix?
Click to expand...
Click to collapse
Different phone. Best not the LG brand?
Sent from my LG-D802 using Tapatalk
PAGOT said:
Different phone. Best not the LG brand?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
The thing is that before this phone I have been using the White one for 6 months and it didn't have this issue.. but 2 days ago I traded it for the Black one and now I don't know what to do.. this thing is so annoying!
rfarrah said:
FWIW, I haven't had this issue at all since the update came out months ago. Maybe they just haven't updated the demo model in the store.
Click to expand...
Click to collapse
whether you'll be kind enough to write a link for what you did two months ago, as you say it is successful and that the problem is solved. I tried to find it but I could not
goran60 said:
whether you'll be kind enough to write a link for what you did two months ago, as you say it is successful and that the problem is solved. I tried to find it but I could not
Click to expand...
Click to collapse
All I did was accept the 12B update. 24A (Kit Kat) is rolling out now, I believe.
I'm sorry for bringing this from dead, but have you guys found any solution for this? Or it's not fixable once it occurs? charging + headphones +v4a developed this bug this evening on my g2.
@PAGOT @goran60 @pitsgraft @Mr.Kos
Closed Force said:
I'm sorry for bringing this from dead, but have you guys found any solution for this? Or it's not fixable once it occurs? charging + headphones +v4a developed this bug this evening on my g2.
@PAGOT @goran60 @pitsgraft @Mr.Kos
Click to expand...
Click to collapse
My ears or better brain adjusted... same way you adjust to every annoying sound after a while. It is there... but you stop caring - hearing it.
I do not believe there is a software fix. If your problem is the one that I described, new hw might help.
But as I said. I adjusted ...
Definitely seems to be hardware problem. If I knew about it earlier I would never connect headphones and charger at the same time. Symptoms: static noise @ approx. 120bpm from both speakers, while phone in deep sleep.
Tried uninstalling v4a drivers, app, poweramp, flashing different kernels, clearing caches, and what so not.
I don't want to raise hope, but I found temporary workaround. I'm on stock kk, and I use g2 tweaksbox and gravitybox to get statusbar aosp quicksetting tiles. There is a compass tile. If I leave it ON there is no more noise. At first I thought that maybe this prevents phone from deep sleeping, but bbs is showing that phone sleeps well. Have not tested standby battery impact yet.
Closed Force said:
I'm sorry for bringing this from dead, but have you guys found any solution for this? Or it's not fixable once it occurs? charging + headphones +v4a developed this bug this evening on my g2.
@PAGOT @goran60 @pitsgraft @Mr.Kos
Click to expand...
Click to collapse
Hi,
Thanks for the remainder, as I noticed latest @dorimanx kernel eliminates this (from v 8) and my itchy fingers installed Viper4Android again and yes I struck my luck the distortion starts again...
My conclusion is an option between have better audio performance in mid to high volume level. But, lived my days with G2 enjoying the distort...
Or uninstall everything about viper4android and listen to flat music beat...
And I choose ingore the distort and drive away with awesome audio performance in my bluetooth car audio....
Cheers,
Hey, do you have xposed? I noticed that if I enable compass in quicktiles, there will be no more crackling. But I'm not sure about battery. So I use this when it's quite, in the evening, and I start hearing cracks, I just turn on compass.