Related
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.
I haven't found any definite information on this issue so that's why I'm starting a thread.
Yesterday, I noticed during a call that I could hear nothing but saw for certain that I was connected to a call and that call volume was all the way up. When I tried speakerphone, everything was normal but as for the built-in earpeice, nothing. The same goes for Bluetooth, everything works normally, but once again, with the ear piece that you out to your head in a normal call, no luck.
WHEN I NOTICED THE ISSUE:
I have been using CM9 nightlies for quite some time (with h0tw1r3's kernel) and had no problems until yesterday when I flashed the Black Star stock ROM out of curiosity of stock functionality. I never made a call in the Black Star ROM to know for certain if the issue took place immediately after flashing it before I had already reverted back to CM9 where I found the issue for the first time.
WHAT I'VE TRIED:
I have already tried flashing three different ICS ROM's (including the Black Star ROM again) wiping EVERYTHING including not only /system, /data, /cache, and Dalvik, but even the internal SD and my external just to rule out any corrupt data that could be interfering. No luck...
Although I've personally never experienced any issues with audio since SGH-i717 development really began, I remember reading that a few people had some audio issues with ICS along the way and am wondering if this could be related. At this point though, I'm thinking it's a hardware issue and not software so I'm expecting to have to replace the phone, although this didn't happen until I flashed the Black Star ROM yesterday which is odd or coincidental if it is solely a hardware failure and not software.
I may try and see if I can get a warranty replacement by resetting the flash counter and leaving only the stock download mode with no third party recovery before I send it in.
But, before I go through the trouble, is there anyone who has encountered or is familiar with this issue that can propose a possible solution?? I'd be extremely grateful for any assistance and would gladly make a significant monetary contribution to anyone providing a solution.
***UPDATE***
Replacement SGH-i717 has been dispatched to me through Samsung warranty. They didn't have any issues or hesitations about replacing my phone for this issue which leads me to believe they've seen it a few times already so for those of you having the same issue, don't hesitate to call in a warranty replacement! I'll let everyone know if Jelly Bean runs better on my new device to answer the question or whether some Notes have defective GPU's that don't work with project Butter or not.
Thanks,
If it persists from rom to rom then logic would say it must be a hardware issue. Get your phone back to stock and get your replacement
Sent from my SAMSUNG-SGH-I717 using xda premium
jpoirier587 said:
If it persists from rom to rom then logic would say it must be a hardware issue. Get your phone back to stock and get your replacement
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I thought so too... On the phone with warranty now! Maybe my replacement will work better with the current Jelly Bean previews. As of right now, Jelly Bean runs less smooth than ICS for me.
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
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.
I've been having issues where I will make a call or receive a call and the other person can't hear me. It doesn't happen every call which is strange. The microphone works in Google Now and other apps.
I'm on the new firmware 4.13 and currently running Viper 4.0.0 though the issue started earlier when I was running Sin's Sense 5.5 rom. Before switching to Viper 4.0, I re-ran the firmware zips from Capt which wiped my internal sd and did a full wipe, but that didn't seem to help. I have not done the official HTC Ruu yet. I do not use PCs at home so I've not had access to a stable PC yet. That is the next thing on my list to try but I'm wondering if anyone else has experienced something similar.
I've tried cleaning the microphone holes, both the one at the bottom and the one at the top. It happens some times and not others which makes it hard to track down.
Thanks for any help!
Your mic is probably beginning to fail. The same thing happened to my first Evo LTE that I purchased. The entire process took about 2-3 months. Eventually, it might stop working completely.
While I'm not saying that this is definitely the case for you, it is very likely, as I had the same experience. Reflashing your firmware should be the first step, then run a RUU if the firmware flash doesn't help. If not, you might need a new phone, buddy.
My main advice is to activate Sprint TEP insurance from now ($5 per month), if you dint have any. Depending on the problem, they replace your device for free. But you can't enter Sprint with the problem.
aarsyl said:
Your mic is probably beginning to fail. The same thing happened to my first Evo LTE that I purchased. The entire process took about 2-3 months. Eventually, it might stop working completely.
While I'm not saying that this is definitely the case for you, it is very likely, as I had the same experience. Reflashing your firmware should be the first step, then run a RUU if the firmware flash doesn't help. If not, you might need a new phone, buddy.
My main advice is to activate Sprint TEP insurance from now ($5 per month), if you dint have any. Depending on the problem, they replace your device for free. But you can't enter Sprint with the problem.
Click to expand...
Click to collapse
Thanks! As this problem has been happening more often in the past few weeks, I bit the bullet last night and ordered a M8. Darn, I just had to upgrade... hehe
But your comment does touch on another question I had. I guess Sprint still offers more than one level of insurance? I used to have the full TEP for $11 per month, but cancelled it after I was due for a new phone. I bought the M8 and added it back on, but with HTC's new screen replacement policy, I'm wondering if I should try to downgrade the full TEP to something smaller, and less $ per month. Is there still a lower tier?
I have the same issue on my Evo but I think mine is related to the bottom of the frame not being fully connected to the phone (brother dropped it a lot). Anyone think that could be the issue?
Sent from my EVO using Tapatalk