My left speaker makes no sound regardless of what app I use including a stereo audio test from the market.. is this common?? During the test if I click the left speaker test it plays very quietly through the right speaker. The right speaker tests fine.
Im running zpad 3.0..
Have you ever opened the device? The speaker wires are very close to the latches and can be affected if you don't close it properly (yes, I have had this exact issue, myself).
No, I just bought it last night.. haven't done anything except clockworkmod and tested zpad 3.0 and now tnt lite..
Sent from my Evo 4G running AvaFroyo w/ MakMod using TapaTalk Pro
I've decided to return the gTab for a refund.. too many issues at this point. I hope the Xoom is reasonably priced, that'll be my next tablet.
Same thing
I've never opened my device, and I have this same issue. Any suggestions?
Same here
I am working on being less verbose. Clearly, it isn't going well.
I just noticed this today, though thinking back I think it has been the case for a while. Also, the problem is intermittent (or dependent on the particular program I am running). On Angry Birds, one speaker, on the FPS benchmark program I use, both seem to work (though I lack adequate sample data at this time).
I have never opened it. I was outside in the sun for a while with it, and placed it on the patio table upside down. It was pretty warm when I picked it back up, so I am curious whether that could be the culprit (and my screen now seems to be less responsive).
Until this I seem to have gotten really lucky. I have never had any problems whatsoever with the G. I have flashed and reflashed. Forgot to wipe data etc., once or twice, and it never made any difference.
Completely unrelated: Also, I am now on my 5th flash of Vegan 7 RC1 (I like to play with other ones, but always end up back with Vegan), and my available memory has increased generally. I did not do anything that I am aware of, except set the CPU to 1400 for experimental purposes. Anyway, once I kill most tasks and cached processes, free memory consistently around 310. Never used to go above 280 no matter what I killed.
Related
I have some problems with my audio in general.
1. In-call volume is very low for me, but it is fine on the other end. I have my volume setting all the way up.
2. When watching videos or listening to music, it will lag very badly and make a weird clicking sound on both speaker and headphones.
Any help is appreciated, thanks.
I have viperXL+ on AT&T
Sent from my HTC One X+ using Tapatalk
Those two issues are unrelated.
The first with the in-call volume has to do with your speaker grill being clogged with dust. It's supposed to be able to be cleaned with a toothbrush. I've also read that wet wipes or some type of tacky silly putty works too. Nothing I do really works perfectly. I took my phone to the store and got a refurb to find the same thing happened a month or two later. Ugh.
Your second issue has to do with the processor not being able to handle the audio processing properly. The clockspeed of the CPU is constantly truing to "step-down" or lower it's frequency to save battery. The CPU's clockspeed is also linked to the GPU. There's something terribly wrong with the way that the processor and it's software are designed. All I can really say to fix that issue is to deal with it. Make sure your OS is stock because it doesn't really happen all that often.
Also, I'm not 100% sure about my second theory, but there isn't really a solution to it right now and I think that's a pretty good reason why.
My Nook HD is rooted and this issue has happened with every ROM (cm10.1 official, cm10.2 nightly, verygreen cm11 unofficial) I've used. If the volume is up and a loud sound it played, is crashes and turns off my device. I have to turn it on again. It hasn't hurt anything that I've seen. My question is: is there an app to prevent this and if so what is it? If not, could somebody make one (I'm not sure if mine is an isolated issue), or teach me to make one (name suggestion: Speaker Keeper) (or show a workaround)? The closest thing that may be causing this is a busted headset jack (not technically busted). It still works, it just is slighty messed up from being dropped on. Two symptoms, one of which I'm not sure if it caused by this, are (sorry if it get's confusing):
1. If I move the headset plug slightly, it will think I have unplugged it entirely, thus triggering the pause of a video if one is playing. I haven't tested this since I've rooted, though I don't think it makes a difference.
2. When using earbuds (well, at least just this one pair, the only pair I could ever find) one of the earbuds (I forget which one. Again, haven't tested it since root, and don't think it woukd be different) made this rattling noise when certain frequency (I believe so. Kinda like speakers that can't process certain sound so they vibrate) sounds played (deep, I think). I think this may just have been a problem with the headphones.
On a side note another thing with my Nook is that I didn't back it up originally when I rooted it with CWM an CM10.1. I still had my personal files after setting up the root, though. Also when it boots up it looks like this https://www.youtube.com/watch?v=GSXxrvE1Ex0&t=5m40s (no, I don't speak... whatever that language is). Could any of this have contributed to this issue?
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Do you remember when were the times when the screen was unresponsive?
I've read somewhere that sometimes when the screen is woken up and is under some pressure this will happen, and the only way is to do what you did. It's not uncommon in touchscreen phones though, so I wouldn't worry about it.
The verge app was broken until the most recent app update. Also, the s5 seems to refuse allowing Dashlane's accessibility service from working properly. So no more auto filling passwords for me. Ugh. I hoped rooting might help but it didn't. Now I really can't wait for custom ROMs to start appearing. Samsung, you make great hardware (like amoled displays) but your software sucks. Even the software on my Samsung TV is stupid.
Yes on two out of three!
finotti said:
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Click to expand...
Click to collapse
The unresponsive screen is more than a little issue, it is being reported all over the web, and get's more severe over time. I'm thinking that it is a bad proximity sensor defect, either firmware, hardware or software. Some people are reporting along with myself that sometimes for no apparent reason, the screen will not turn on even though the phone is completely operational! This has happened to me four times now and I am stock with very few apps on my phone, five total games and Pandora. I do use a substitute launcher that I've used for years but I don't believe that would be the issue since others report the same issue with stock launcher.
The pop or skipping you speak of in sound happens to many of us who stream music in our automobiles. It even happens on the note3. The fix is simple for that one though! Turn the screen on. I was told that with many of the streaming software music programs that the phones CPU goes to sleep and does not offer enough processing power to the music program. I stream all day via bluetooth to my Auto's sound system and it will usually start to skip, click or whatever after the phone has been untouched for about twenty minutes. The second I turn the screen on the problem alleviates itself. You can find even more information by googling that one, in fact both of those! The heat one I have not had, both with stock battery and zero lemon high capacity battery. The phone very rarely get's warm. However, when I was using wireless charging it would get warm even after charging was complete but I believe that is a normal event with QI type tech.
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Kazz5 said:
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Click to expand...
Click to collapse
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
I read this reply via email before taking the time to come here and I just want to say thanks for such a thorough sharing of your experience and perspective! You made it clear to me that ordering a Shield was the right thing to do in my case. Interestingly, my Nexus 9 did the squeal/crash in another app soon after I posted this.
My Shield came in, upgraded painlessly, OTA, to 7.0.0 and seems to run much smoother than the Nexus 9 in every way. Yes, the screen is a bit smaller. But, frankly, I'm seeing less pixelation - I have to assume - due to the smaller screen size. The Shield runs cooler (I used to blow on the hot end of the Nexus 9 when holding it in my hands, in it's case, for longer periods of time) and the battery definitely lasts longer.
I will finish moving everything over to the Shield in the coming few days and make up my mind what I want to do with the Nexus 9. With it's large size and 4:3 aspect ratio, I may relegate it to electronic magazine reading - of which I have a few. I saw a reference to running some flavor of *nix on it. That could be interesting. A touch panel for security cameras is a thought, if do-able, as well. I'm sure more thoughts will come up, including getting a more stable Android installed on it.
Please keep me/us posted on your experiences with the Fire-Ice kernel! And thank you again!
GedBlake said:
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
Click to expand...
Click to collapse
I wanted to follow-up with you on an experience. I moved to the Shield K1 and have been using it since May. Something's happened with it's charging (I suspect the mini-USB port's connection as it seems to be a weak spot for many). In a pinch, to keep playing my game of choice, I picked up my Nexus 9 and gave it a full charge. I was thrilled since it was working so well. But once it hit 58% charge the weird screen and shrill shrieking returned. Now cornered, I did my best google-fu and uncovered a couple of threads that claimed I could fix my Nexus 9!
It seems many people were having success with removing the back panel (easy), gently prying a small, metal cover off of the battery's connection at the circuit board, unplugging the cable, cleaning connections with isopropyl alcohol, and re-assembling. I found a Youtube link (ifixit, I think?) there that showed how to disassemble the Nexus 9 and I was off! It seems some folks have had this clear up the problem for months and some have had it recur, fixing it again with the same procedure.
I've been using it for days in all states of charge with no return of the problem so far. It's given me plenty of time to get my warranty-replacement Shield enroute. The Shield is still much quicker. But I'm thrilled that there's not some odd gremlin with the Nexus 9. I knew I needed to track this post and your reply down in order to let you know. I hope it helps you and/or someone else!
And thanks again!
Just wanted to bump this thread as I am having the same problem with my N9 and it is steadily getting worse. When this problem first started, it would happen once every 2-3 weeks, usually when I was in Instagram. Now it is happening daily, or multiple times in a day, and sometimes it occurs right after reboot.
I have gotten frustrated enough that I am going to do a clean (reflash) of Pure Nexus, ElemX, etc and see if that has any effect.
Did you read my reply? Cleaning the connector to the battery has fixed my issues - which were constant - for weeks now!
I just got one of these Nexus 9 32GB giving to me by a family member as they upgraded to something else due to the issues with the Nexus 9 . It had the whole deal going on with the white pixelated screen freezing followed by a loud ear busting screeching noise at roughly 50% and 20% battery. I factory reset the tablet and cleaned the cache in recovery then popped back off the tablet and disconnected battery for a min or two, hooked it back up and it runs like butter so far for the last week through the whole cycle of the battery without freezing or screeching. Strange indeed but that fix works for whatever reason.
Hello. Picked up an Xperia X a couple months ago and have been generally happy with it, though I'm having some bluetooth issues ranging from annoying to infuriating that are preventing me from really enjoying this phone. Hope some of the gurus here can provide a some guidance on what I can do to fix or workaround these issues.
1. After some period of time listening to music/podcasts/whatever, the phone will automatically drop the volume by half and display the message:
Listening to sounds above the current volume level may permanently damage your hearing.
That's fine and dandy, but I'm controlling the volume through the bluetooth device, and the result is that it drops to a volume so low I can no longer hear it, and while it's a simple thing, it's infuriating every time it happens. Based on prior searches, I know this is a built-in "feature" and I know it's been part of the Xperia phones for a while, but is there any way to disable this behavior? I have my phone rooted, so root-level apps, Xposed modules, etc. are all on the table. This is my number one complaint with the phone, so would really appreciate any help here. Note: to clarify, I want to stop this *behavior*. I've found other discussions about killing similar warning messages, but nothing about how to prevent it from actually lowering the volume.
2. When connected to my car through bluetooth, I don't get metadata from the phone (AVRCP?). Bluetooth problems in general appear to be widely reported for Android 7.1.x on this phone, but most people seem to complain about being unable to pair their device at all. I can pair it fine, but I don't get metadata. However, prior to upgrading to 7.1 (while still on 6.0) metadata worked, and when running OmniROM 7.1.2 on this phone metadata also worked. So, it seems to be a problem with this particular version of the stock ROM for this phone.
Any ideas on how I can fix that? Again, maybe an xposed module or something that I've overlooked? or could I maybe swap out the bluetooth stack from OmniROM, which works fine? This is a much lesser annoyance than the above, but still interested in any suggestions.
3. Finally, this is a more subjective issue, but does anyone else have problems with bluetooth performance in general with this phone? On my last two phones, I kept my phone in my left pocket and played through a bluetooth headphones with the receiver on my right ear with generally no problems, other than the occasional hiccups that seem to affect every android device (at least every one I've used). With the Xperia X, however, trying to play with the phone in my left pocket skips so horribly that it's completely unlistenable. Moving it to my right pocket helps somewhat, but it's still flaky - turning my head sideways such that the receiver is over my shoulder causes skipping. I have to move my phone up into my jacket pocket in order for it to play (mostly) reliably.
Does anyone else have problems like this? Again, I never hard this problem with either of my two previous phones on the same set of headphones (have similar, but not as severe, issues in my car as well). I *did* have this same problem with OmniROM as well, and I have the problem with and without a case, so it seems hardware related, but if the bluetooth hardware was truly this bad I would expect to have seen more discussion about it. So, just wondering - is this just me, or do other people have this problem as well? I know it's unlikely, but any suggestions to improve this? Ie., possible to increase the bluetooth transmitter power or something like that?
Thanks, all. Sorry this turns out a little long, just wanted to properly explain. Looking forward to any suggestions.
I can confirm that on my XX Bluetooth signal is also weak, I have same issues at least with two Sony headsets (SBH60 and SBH80). Also with Bluetooth AptX receiver for my (home) audio it is quite similar, just walking behind corner from direct visibility and audio is choppy...
1. This error message appears very rarely, for me, not every 30 minutes. I have this phone for 1 year now and I encountered the warning 5-6 times.
2. Idk
3. True, Im pretty dissapointed by the bluetooth strenght. Also, the WiFi is super weak too. Very dissapointing.
This also happens on the Tablet Z, where I have external speakers connected. Nannytech run amok.
Replying to old thread, but got just new bluetooth headset and noticed also very poor bluetooth performance on my xperia x. Distance between phone and headset cant exceed half a meter, or music starts stopping and skipping. Even with my ancient backup phone, Iphone 4s, distance can be meters... Very poor desing from Sony.
Bluetooth in general eventually drove me away. Only got midling performance at best, but whatever chip or driver or whatever they were using also had performance issues with custom ROMs. Never found a single ROM not based on stock that worked 100% correctly with bluetooth, and given podcasts and music is probably about 90% of what I use my phone for (combined with Sony ending even security updates long ago at this point), that was a pretty big problem for me.
Ended up buying a Pixel 3a to replace it. My main concern about the 3a is that I wish it was a little bit smaller (really my concern with almost every well-spec'ed phone these days), but the bluetooth in that phone is solid. Longer range and better strength than any other bluetooth device I've ever used. Extremely happy with it.