So I've looked at other threads and can't find any advice about this static issue I'm having.
First of all, I'm on Vegan Ginger 7.0 and that's all I've done with the tablet.
When I first boot the device sound works fine. After a while the sound get static-y...then becomes just static.
Is anyone else having this issue and I just don't know how to search the forums?
~JohnnyB~ said:
So I've looked at other threads and can't find any advice about this static issue I'm having.
First of all, I'm on Vegan Ginger 7.0 and that's all I've done with the tablet.
When I first boot the device sound works fine. After a while the sound get static-y...then becomes just static.
Is anyone else having this issue and I just don't know how to search the forums?
Click to expand...
Click to collapse
About 90 minutes after I made this post someone made another one. It seems it's a defective tablet and I'll need to flash back to stock, then exchange for a different one.
Might want to try plugging headphone in and removing them. MIGHT take care of the issue
diablokicks said:
Might want to try plugging headphone in and removing them. MIGHT take care of the issue
Click to expand...
Click to collapse
Yep, I just figured out how to properly use the "Search" feature of this forum and found my "answer" over on a development thread for Vegan 7. I don't have my first 10 posts yet so I can't respond to it but at least I found where they suggested that. There was a caution issued for this fix though. It was mentioned that there are only two "shoddy" solider connections on the head phone jack and that over use could easily wear them out.
I did notice that after the upgrade from 5.1.1 to 7.0.0 the sound issue had gone away for several days. It's come back and I've been systematically wiping various caches in an effort to identify a potential culpret. This morning I wiped cache partition and haven't had any issues in a few hours. We'll see how long that lasts....
Well, I must go find some other things to post so I can get back to the development thread and try to troubleshoot this sound issue further.
Sounds like hardware. Like you said restore it to original, and return it.
Related
Hi, I'm a bit of a newbie to XDA, but I came across a problem which I browsed the forums and the internet for a few hours to solve to no avail. A few days ago I made a call to one of my friends who apparently couldn't hear anything from my side. I checked this over and restarted my phone a few times to see if that would fix it. Unfortunately the problem persisted, and when I tried to record any audio, all I would hear from the playback is noise. I assumed that it was a faulty flash of Trigger v2.8, but ODIN'ing back to stock didn't seem to fix the problem. I use the phone in Canada, and won't be visiting the US anytime soon, so I can't go to a T-Mobile booth to get it checked out. Is there anything I can do? Any help is greatly appreciated.
check settings and make sure you do not have anything off, that could happen, But if you can't resolve find a compatible kernel for your ROM and try flashing that. That usually will fix most problems.
Good luck
Thanks for the help, but I was unable to fix the problem using these methods. I'm starting to believe it is indeed a hardware problem, but I would want to receive some more input and where I should take it to be fixed if that's the case.
I am sure several people have posted about the static issue on this tablet. In case nobody here has, at random intervals the tablet will make a loud hissing sound (regardless of volume or sound settings). A reboot will fix this, but not permanently. My two questions are:
Is there a fix for this that I can perform?
If not, can I send it in for a replacement from Woot or Viewsonic? (only had it a day)
I think you should send it back. I had the same issue and finding no solution here or on other forums I emailed woot for an rma. I got an email back the next day with return shipping instructions and shortly after that another one to tell me they shipped the replacement tablet.
At first I wasn't sure if it was a fault with the rom (Vegan) I put on. I never really tested it for sound while it was stock and did not notice the problem. Once I put it back to 3588 to send it back, it did the same thing: static noise after coming back from sleep or no sound at all if it was on mute before it went to sleep.
I'm glad I sent it back, the new one works perfectly.
Alright, thanks! I have run into a problem, I tried the solution for reverting to stock found here http://forum.xda-developers.com/showthread.php?t=861950 but I am stuck in an infinite loop of the Tap n Tap load screens, and the tablet never loads. Any ideas?
I'm sorry but I can't help you there - I didn't use NVflash. But I saw lots of posts about the same boot loop problem, so you might find a solution searching the forum.
mrtoolman said:
Alright, thanks! I have run into a problem, I tried the solution for reverting to stock found here http://forum.xda-developers.com/showthread.php?t=861950 but I am stuck in an infinite loop of the Tap n Tap load screens, and the tablet never loads. Any ideas?
Click to expand...
Click to collapse
You need a data wipe. Try this: http://forum.xda-developers.com/showthread.php?t=1030915
kaffeesnob said:
I think you should send it back. I had the same issue and finding no solution here or on other forums I emailed woot for an rma. I got an email back the next day with return shipping instructions and shortly after that another one to tell me they shipped the replacement tablet.
At first I wasn't sure if it was a fault with the rom (Vegan) I put on. I never really tested it for sound while it was stock and did not notice the problem. Once I put it back to 3588 to send it back, it did the same thing: static noise after coming back from sleep or no sound at all if it was on mute before it went to sleep.
I'm glad I sent it back, the new one works perfectly.
Click to expand...
Click to collapse
Hmmm, I bought mine from Office Depot. So, I should be able to flash it back to stock and just make the exchange.
The only way for people to hear me is if I am on speaker or using a head set. I've tried many different roms all with same results except cm10 people can never hear me (not tested with headset, only speaker). I believe my phone is using the top mic (noise canceling one) as opposed to the one at the bottom. When I talk into the top mic I am being heard but I am still very hard to hear.
Does this sound crazy? Anyone have any idea how to fix or why this randomly happened?
Got the same problem but my speaker Mic doesn't work either. Gonna have to get me a Bluetooth cause I can't take it back to Sprint cause there's no RUU for 3.16
Wreaking havok from my EvoLTE CyanogenMod 10.1
S-on
Did you really have to make two threads for the same question. Bad etiquette!
But, did you do a "FULL" wipe before flashing a ROM? If yes, perhaps you should run RUU to go back to complete stock then start over. If that doesn't solve the problem, not sure.
wolfclan68 said:
Did you really have to make two threads for the same question. Bad etiquette!
But, did you do a "FULL" wipe before flashing a ROM? If yes, perhaps you should run RUU to go back to complete stock then start over. If that doesn't solve the problem, not sure.
Click to expand...
Click to collapse
I created a thread even before his addressing the same exact issue. My issue was a result of a faulty device replacement from sprint. I had to get another replacement from sprint to resolve the issue. I suggest you do the same, but you can try a clean wipe and flash a stock rooted rom and see if the problem persists. If it does I would take it to sprint and get a replacement.
P. S. Next time search first before posting because I did address the same exact issue about a 3 weeks ago
Sent from my Viper'd LTE
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
Hello! I just got a new unlocked HAM2 from B&H yesterday. It works really well, but one thing that is kind of weird about it is that when you boot it there is a very, very quick flash of snow (like when an older television has no signal or the HBO logo snow) right before the Huawei logo bootscreen. Otherwise, the device seems to be working normally. It has the latest stock firmware installed from box and I have done no modifications to the phone. I was just curious if anyone has this strange, seemingly harmless glitch on their phone on boot or reboot. Also, is it something to exchange it over? I guess I was just worried it was a hardware problem or something that might get worse in the future. I know I have had Linux machines that do strange things in the past when initializing video on boot, so maybe it's just a software issue with the stock ROM. Thanks so much.
Weird. I've never heard of this before.
If you just got it, maybe you could try doing a reset? Resets have fixed some bugs for me and possibly a few others.
ScoobSTi said:
Weird. I've never heard of this before.
If you just got it, maybe you could try doing a reset? Resets have fixed some bugs for me and possibly a few others.
Click to expand...
Click to collapse
Thanks so much for your response. I just tried a reset but no luck. I used the VOL UP plus POWER method on boot to do it. I just posted a few screenshots of a video I took to give you an idea of what it looks like. On the off state, two during the snow state, and one after the snow state (seemingly normal). Imagine it as a very, very fast flash. If you blink you miss it. Probably happens over the course of just half a second. Maybe it's something to do with the LCD panel initializing or something.
EDIT1: I also wanted to note that the screen does not do this when it goes to sleep or is woken from sleep. Only during the initial powering on of the device.
EDIT2: One more note, the device came with build MT2-L03V100R001C00B148 installed from factory.
deploypenguins said:
Thanks so much for your response. I just tried a reset but no luck. I used the VOL UP plus POWER method on boot to do it. I just posted a few screenshots of a video I took to give you an idea of what it looks like. On the off state, two during the snow state, and one after the snow state (seemingly normal). Imagine it as a very, very fast flash. If you blink you miss it. Probably happens over the course of just half a second. Maybe it's something to do with the LCD panel initializing or something.
EDIT1: I also wanted to note that the screen does not do this when it goes to sleep or is woken from sleep. Only during the initial powering on of the device.
EDIT2: One more note, the device came with build MT2-L03V100R001C00B148 installed from factory.
Click to expand...
Click to collapse
By "snow", do you mean static or noise? The screen looks a bit staticy or noisy in those pictures. The only thing I can think of is maybe some of the animation images are somehow corrupted. The boot animation is just a bunch of .PNG images shown in succession pretty quickly. This might explain why you see that stuff in a split second every time you boot.
Same here, as of today. I've owned mine for about 3 months, and it just did the static-y flash thing you explained. I remembered this thread, actually, so when it happened I decided to come track this thread down.
Mine is rooted and tweaked, however. Stock ROM, unlocked bootloader. Everything has been mostly fine (except my phone learned a new trick it likes: "Flip the video orientation randomly when someone's watching youtube! Yay, upside-down!"
Other than the occasional tempermental quirks, it's been running smooth. So I'm not sure of what could be causing this. But if more people state theyre having this issue, maybe it'll be further looked into!
zombunny said:
Same here, as of today. I've owned mine for about 3 months, and it just did the static-y flash thing you explained. I remembered this thread, actually, so when it happened I decided to come track this thread down.
Mine is rooted and tweaked, however. Stock ROM, unlocked bootloader. Everything has been mostly fine (except my phone learned a new trick it likes: "Flip the video orientation randomly when someone's watching youtube! Yay, upside-down!"
Other than the occasional tempermental quirks, it's been running smooth. So I'm not sure of what could be causing this. But if more people state theyre having this issue, maybe it'll be further looked into!
Click to expand...
Click to collapse
Sounds quite odd, never read about this until this thread.
As for the upside-down video, check your root tweaks or display settings.
ScoobSTi said:
Sounds quite odd, never read about this until this thread.
As for the upside-down video, check your root tweaks or display settings.
Click to expand...
Click to collapse
It is odd, hopefully it's nothing serious to worry about. It'd be a shame if it were to become a problem, as I've really been enjoying this device.
And I've been checking about the video orientation bug, but I can't think of anything I may have changed that would alter it. It's very random, and seems to only occur within MX Player. May be limited to that app only. A reinstallation might fix that, but configuring the orientation to "force auto-rotation" within the App Settings module has ceased the issue.