Related
Over the past 2 years I have had 3 separate and different mobile phones. Each with their own problems.
1st a htc hero which had many problems , not anything which needed it sending back but things such as push call and it wouldn't call anyone for 5 mins then place 15 calls to that person. Not sending texts and dropping calls.
2nd a htc desire hd , got the day of release , sent back 4 separate times. Faulty phone which drained the battery dry in 3 hours even when not using it . Another twice for the phone dying and not switching on. And then a problem with the screen not displaying anything aswell as each time taking a photo it would switch the phone off.
3rd and finally the iPhone 4 which I have had for 2 months , and granted to software is a lot more stable than android (and more boring even when jailbroken) but even this phone has a fault with the light sensor so the screen dosnt re illuminate when making a call.
Is it just my bad luck or as phones are packed with more gizmos and gadgets are they becoming less reliable? Because as you can see here the more advanced the phone gets the more issues arise. Now I'm not complaining i think even with the faults there is no way I could live without a smartphone.
Any comments or are other people feeling this way ?
no, in our environment where broadband and instant gratification has become so pervasive our expectations have risen ... sometimes to unrealistic levels
Bummer...fortunately I've had no big issues with my last 3 HTC devices!
I think they're generally just as reliable as before, which is to say not very reliable at all. There's not enough testing and quality control and, as ever, new technology is constantly replacing the old before the old is ever perfected. That applies to both hardware and software where it seems every iteration brings a new set of problems.
Also consider how much more frequently they are used as opposed to the days of the Nokia 33** phones, voice only, no such thing as texting or data.
The more features you have the more these is to go wrong...
omgjosho said:
Also consider how much more frequently they are used as opposed to the days of the Nokia 33** phones, voice only, no such thing as texting or data.
Click to expand...
Click to collapse
This.
Or it is probably your luck
From reading your post, I'd say the majority of the problems lies within the user. It's like giving an inexperienced 18yo a classic Ferrari and expect the kid to know on how to properly take care of it. Maybe it's the case of TOO much technology for one to handle rather than phones becoming more unreliable. Funny how I've had about 4-5 phones in the last 2yrs and none have gone in for repair.
All phones now are unreliable crap. . . . All the way from beyond garbage software that needs to be changed to for even daily use(that is why this community exists), to junk hardware.
Windows 7 < enough said
As an ex-Android and WinMob user I can only agree, phones are unreliable ... and lets be honest, they have been for more than a couple of years!
The problem as I see it with OS's like WinMob and Android - they are written to be "everything to everyone". They are then customised either with drivers or a front end or both by a manufacturer and this is where the weak points come in.
Why do you think IOS and WinPho7 are far more stable? Because they are closed environments with restrictions to hardware access/low level coding. Because of this its much harder to introduce unstable code.
I am now a Winpho 7 owner and I cannot express here just how happy I am with its stability. OK, it *currently* doesn't do everything Android and WinMob do but what it does do, it does reliably
How embarrasing was it when you went to give a friend a phone number and your "contacts" would lock up or, you try to make a phone call and nothing happens or, you don't get phone calls ... only to find out your phone had locked up!
Reliability is now 100% key for me.
omgjosho said:
Also consider how much more frequently they are used as opposed to the days of the Nokia 33** phones, voice only, no such thing as texting or data.
Click to expand...
Click to collapse
dont be rediculous.
I've been using phones as "modems" for years, probably actually thinking about, over a decade! As as for "no such thing as texting"......
jordanprudent said:
Over the past 2 years I have had 3 separate and different mobile phones. Each with their own problems.
1st a htc hero which had many problems , not anything which needed it sending back but things such as push call and it wouldn't call anyone for 5 mins then place 15 calls to that person. Not sending texts and dropping calls.
2nd a htc desire hd , got the day of release , sent back 4 separate times. Faulty phone which drained the battery dry in 3 hours even when not using it . Another twice for the phone dying and not switching on. And then a problem with the screen not displaying anything aswell as each time taking a photo it would switch the phone off.
3rd and finally the iPhone 4 which I have had for 2 months , and granted to software is a lot more stable than android (and more boring even when jailbroken) but even this phone has a fault with the light sensor so the screen dosnt re illuminate when making a call.
Any comments or are other people feeling this way ?
Click to expand...
Click to collapse
It beggars belief that people are saying that these are YOUR fault and the way you use it.... unless of course you decided to throw it on the floor (which i doubt!)
So all those "its your fault" people, how would he/we break a light sensor or stop the screen switching on? Seriously .. would love to hear this!
DirkGently1 said:
I think they're generally just as reliable as before, which is to say not very reliable at all. There's not enough testing and quality control and, as ever, new technology is constantly replacing the old before the old is ever perfected. That applies to both hardware and software where it seems every iteration brings a new set of problems.
Click to expand...
Click to collapse
Would have to 100% agree with this! Too much rush, not enough QA.
no, in our environment where broadband and instant gratification has become so pervasive our expectations have risen ...
Monty Burns said:
dont be rediculous.
I've been using phones as "modems" for years, probably actually thinking about, over a decade! As as for "no such thing as texting"......
Click to expand...
Click to collapse
I'm hardly being ridiculous. It's common sense. If you leave your car in the garage 6 days out of the week and only drive it on Saturday, the probability of failure is significantly lower than if you were to commute daily. There are a number of factors involved: mechanical failure and accidental damage being two examples.
The same could be said of cell phones - when they had less function than the phones of today, there were fewer points of failure and a lower probability that it would occur.
Just because you may be the exception to the rule does not change the rule. Assuming that is ridiculous.
omgjosho said:
I'm hardly being ridiculous. It's common sense. If you leave your car in the garage 6 days out of the week and only drive it on Saturday, the probability of failure is significantly lower than if you were to commute daily. There are a number of factors involved: mechanical failure and accidental damage being two examples.
The same could be said of cell phones - when they had less function than the phones of today, there were fewer points of failure and a lower probability that it would occur.
Just because you may be the exception to the rule does not change the rule. Assuming that is ridiculous.
Click to expand...
Click to collapse
I wasn't refering to the complexity=failability, couldn't agree more!
I was refering to the fact that you suggest that people didn't text or use mobiles as modems, of course we did.. The only diference was that we had a modem cable and proprietry dialer! I even setup an NT4 RAS server for our company...
and texting? Your seriously suggesting texting is a "new" craze....? I might suggest the exception to the rule might be you.
I was referencing the period before SMS was an available service, actually. So you're missing the point.
And the majority of people were not setting up their cell phones as modems on NT4, so you are still missing the point and bordering irrelevancy.
Regarding SMS... I sent my first text message before making my first mobile call...
Regarding reliability, my previous phones (roughly £100 dumb phones) were all useless.
Friend has LG cookie. Worst, least reliable phone known to man.
Hero? Used it heavily for 16 months out of my 18 month contract, and still not seen anything that takes my fancy to replace it comes May...
Best, most reliable phone has been the most recent one.
For those who complain of a device's speed, just whip up a custom rom and optimise it.
Never had any speed issues on my own ROMS... had plenty in others
omgjosho said:
I was referencing the period before SMS was an available service, actually. So you're missing the point.
And the majority of people were not setting up their cell phones as modems on NT4, so you are still missing the point and bordering irrelevancy.
Click to expand...
Click to collapse
I'm guessing your in the USA where adoption of digital networks was far slower (and later) than in the UK (and probably Europe?).
Texts have been an integral part of mobiles since well before your Nokia 33xx models i.e. before 2000.
For example, my first mobile was on Hutchinson Telecom (now Orange) back in 1995 Linky
And do you even know what NT4 RAS was? You wouldn't put a mobile on it! You would use a Win95/98 client to dial into it ... usualy from the laptop with its modem i.e. cellphone! Here in London it was common place for IT support to carry this kind of setup around. IT people were some of the first to take advantage of digital networks.... for this very reason. (Yes you could do it over analogue but it was easily monitored)
So, as we are going to labour a pointless point, why on earth do you think texts are a relatively new thing!? Maybe in the states it is but not here in Europe and certainly not in the UK!
edit:
ahh yeah there we go "Location: Livermore, CA" of course, the rest of the world doesn't exist does it...
There's no point debating with someone who's failing to read.
I never once said that texting was a new thing. You put those words into my mouth, and I'm yet to agree with you about that.
Regardless, let me know when you're ready to actually discuss the topic, sans tossing out insults and making assumptions about what I do and do not know
Does anyone know if Verizon will be allowing us to get a tablet with a phone number? I'm not up for a new phone for a couple of months yet (I've got the HTC DINC) but I think that it would be nice to just get a tablet in place of a new phone but still be able to make calls from it.
tablets arnt made for calling people.
Technically it should be possible to make calls on a tablet since they obv have speakers and also a mic (currently used for voice recording) but i dont know if anybody has found a method for it yet. The only problem with having a tablet for a phone would be that it is too big to be mobile (like fitting in a pocket) and idk if they have ringtones or notifications so youd have to use an app that does an led notification on the screen which would be a problem since youd never hear it when you are getting a call. It just does not sound practical at this time, IMHO. P.S. sorry for the wall of text
I completely agree with the portable argument because most people would want to be able to carry their phone easily, but I have a bag with my 95% of the time and don't think that I would mind carrying it the other times. It just feels like I'm going back to the times of carrying my cell phone and my ipod and now it's going to be my cell phone and my tablet.
I didn't even think about the technical aspect. I figured with Ice Cream Sandwich and the convergence of the phone and table distros it wouldn't be a software issue.
Thanks for the reply.
Do tablets have all the needed hardware to work as a phone in a GSM-Network?
I know that many tablets have a simcard slot but thats for mobile internet.
I just assumed that if they could do 3g/4g the could do data too. It doesn't sound like it should be too difficult to do, but maybe it is on purpose to keep people buying multiple device.
T-Reb said:
I just assumed that if they could do 3g/4g the could do data too. It doesn't sound like it should be too difficult to do, but maybe it is on purpose to keep people buying multiple device.
Click to expand...
Click to collapse
exactly. I activate data plans at work for tablets all day. They have to reserve a phone number. Often, they have 0 minute voice allowances but unlimited texting (wtf?)
So, I've searched around quite a bit on this, and the only things I could find were on other devices, not even ones in the moto_msm8960 family, either.
As the title states, I'm getting what sounds like a feedback squeal in my ear when I make a call, or receive a call (doesn't matter which). This does not happen every single call, but it does happen most, almost all, of the time (>=95%). As of yet, I can't determine a pattern of any kind, such as people on a particular carrier, within a certain region or location, or even a time of day. When it does happen, however, the other party can hear static over the line, and it has nothing to do with signal (full bars or no, it's consistent with the squealing I hear). The sound decreases phenomenally when I put the phone on speakerphone, I have to put the phone almost right next to my ear to hear it...but the other parties can still hear the static pretty bad. One person told me it "sounds like [I'm] in the rain" it was so bad, and him living in Florida means he's not talking about a light sprinkle
To answer questions I've seen frequently on similar posts for other devices, and to give you an idea of what I've tried; it does not matter if wifi/GPS/bluetooth are activated. One post even mentioned pocket mode, but that did nothing with I toggled it. The sound does not occur when playing music through the speakers, only calls. On that note, I'm going to reiterate that it does not matter if I'm making or taking a call, the sound persists. I can move the phone away from my face during the call, but it doesn't decrease the sound.
UPDATE: When I make a recording, I can indeed hear the "rain" that the person mentioned above, making me think that it might be my mic.
If this is a hardware problem, I can easily replace the microphone. Spare parts are easy to find, and I'm tech savvy enough and even have the proper tools to replace the parts myself. However, if there's even the slightest chance that this is a software problem, I'd rather see what you guys think first.
Thanks for your time!
This post pertains to the issue addressed in the following thread:
https://forum.xda-developers.com/galaxy-s7/help/dont-s7-s7-edge-users-post-recorded-t3535820
I posted the following to the Samsung support community last week...
Description & Solution
The intent of this post is to offer an easy solution to S7 and S7 Edge owners experiencing the recorded audio crackling issue. I have two devices that were suffering from the problem: an S7 and an S7 Edge. I purchased both devices brand-new. The crackling bursts plagued my recorded video footage as well as my voice recordings on both devices. My S7's crackling issue was bad enough. But on my S7 Edge, the crackling was simply horrible - far worse than my S7 had ever been. I have seemingly discovered a way to eliminate the crackling sounds on both devices.
I came up with this simple procedure myself after many phone calls to Samsung customer support --who would always claim they have never heard the complaint before-- and a great deal of web searching. Like my calls to Samsung, my web searches rendered no viable solutions, nor even a single factually convincing explanation as to the cause of the crackles. There were only mere guesses as to why the crackling perpetually manifests from the audio input circuitry (microphone stage) on certain S7s, S7 Edges and older S model Galaxy devices (dating as far back as the S4). It has been frustrating. And Samsung's repeated insistence that they have never heard the complaint before each of my calls, then reading that other folks were told the very same thing, made my situation all the more disturbing.
So, without further ado, below is my fix. Or at least it has seemed to fix both of my S7 devices - your mileage may vary. And this solution is so simple that it almost makes me want to slap myself for not thinking of it sooner.
Make sure your battery is fully charged and launch your camera app. Tap the 'record' button and set your phone on a table, allowing it to record for at least 1 hour. The crackles appear to be electrostatic charges existing within the audio input circuitry of certain S7s and other older Samsung phones. By allowing your device's audio recording function to "burn in" (as it were) for one hour or more, you should be able to permanently deplete those electrostatic charges, thus eliminating the periodic discharges during your recording sessions and therefore the crackles that superimpose on your video and audio files. You may be able to perform this same burn-in function with an extended audio recording. But since I haven't tried that yet, I don't know whether it would render the same result after just one hour of record time, or whether it may require a longer period.
So that's it. I now have two S7 devices that are finally free from emitting those annoying crackles on my recordings. I can leave either device on over night and make a new video in the morning and it's consistently clean! Please try this method and let me know if it works for you as well.
And I posted the following update to the Samsung support community this morning...
Update:
Since my last post, I've performed this procedure on yet another S7. The result is that now the problem appears to be completely gone on it as well. And I think I've proven something else. I did not perform this latest audio recording burn-in session with the third S7's pre-installed camera app video recorder feature, as was done with my own two S7s. Instead, I used the 'Audio Recorder' app from Sony Mobile Communications in stereo mode to record a 1-hour audio file on the device. But you know what? As with my two S7s, this burn-in seems to have totally eliminated all of the crackles/pops from the device as well. So now it seems clear that you don't have to have a huge amount of free storage available to perform the fix, because you can simply use a long audio recording session.
So the fix is: Simply use a 1-hour audio recording session to bleed down all of the electrostatic that for some reason seems to build up on some devices during the manufacturing process. I'm becoming more and more convinced that this is the solution, everyone. No longer a single crackle on any of three S7s that were previously suffering from the issue! Hopefully S7 owners suffering from the recorded audio crackling problem will find my posts herein and thus be able to easily fix their devices.
At this point, I believe that the solution described herein may genuinely and completely resolve the intermittent, but perpetual, recorded pops and crackles issue experienced on S7 /S7 Edge video and audio recordings by some device owners.
Cheers
Update 2:
Unfortunately, the one-hour audio recording session on the third S7 ended up only reducing the crackles overall. They remained absent for more than 24 hours but then reappeared with reduced intensity. However, because the crackling has in fact never returned on my own S7 and S7 Edge after my video recording burn-in sessions, on Monday I decided to perform a one-hour video recording session on the third S7, too. And I'm happy to report that since that session the crackles have been entirely nonexistent on that device as well. If they return on any of the three S7 devices, I'll report back. If they don't return, the indication will be that a one-hour video recording session seems necessary to fully resolve the crackling issue.
I'm unsure why the audio recording session turned out to be unsuccessful on the third S7 device. I would think that an extended audio-only recording session should do the same thing with microphone input that an extended video recording session would do. But perhaps the extra heat generated during a video recording session is an important factor.
Hi clonk. I've been following your battle against this popping issue and I appreciate you taking the time to share your findings. I've been trying your technique and I can't seem to get it to work properly.
I have a S7 active and I get a lot of annoying popping sounds when I first start recording after not using the camera in a while. I plan on posting them on YouTube or something to hopefully make it more visible to others. I'm surprised it's not already viral.
Anyways, I would start recording and leave my phone alone for about an hour. When I get back to my phone I see the timestamp for an hour, so I stop the video. But when I check the video file I see it split in two parts, one video around 27 minutes then another video for 34 minutes. I think I have enough space on my SD card for an hour long video.
When I check for the crackles it's still there. Any advice?
I was able to record a video longer than an hour last night. I dropped my recording resolution to VGA and I left the phone recording when I went to sleep. Woke up and found a video of 1:40 min long. However, when I tested the camera this morning I switched it back to FHD and still got the popping noise.
_LANTERN said:
I was able to record a video longer than an hour last night. I dropped my recording resolution to VGA and I left the phone recording when I went to sleep. Woke up and found a video of 1:40 min long. However, when I tested the camera this morning I switched it back to FHD and still got the popping noise.
Click to expand...
Click to collapse
Hi _LANTERN. You know, I'm quite puzzled by your failed results, as well as by the failed results of another individual who tried my method in order to resolve his S7's mic input crackling issue. He has been communicating with me on the Samsung Community support forum. It doesn't make much sense because both of my own S7s, as well as my friend's S7, are still crackle-free (as they have been since the completion of their respective video burn-in sessions). I simply can't account for why you haven't enjoyed the same results.
I can tell you that my S7 rendered exactly the same file splitting result from its 1-hour video burn-in session. I ended up with a 36 minute file and a 28 minute file. I'm unsure why this happens. My friend's S7 produced multiple files, too... but I can't remember their durations. My S7 edge, on the other hand, recorded clean though its session rendering a single file with a total runtime of 1 hour and 5 minutes. The only difference is that my edge has a 256 GB SD card and my S7 does not. I'm unsure whether this may somehow be a factor.
At this point I am absolutely clueless as to why the two of you (unless the person on the Samsung forum is you as well) have not experienced the same favorable result that we have experienced with the three S7 devices here. The crackling is entirely gone on each of them. Period. I simply can't imagine why the story isn't the same in each of your cases. From your descriptions, it sounds to be the identical source problem. This is indeed a mystery.
I would try at least one additional burn-in session. I used FHD 1920x1080 mode for the sessions on each of the three devices here. I left each device in record mode and pointed at the ceiling in a dark room. If you try another session, please report back.
clonk said:
Update 2:
Unfortunately, the one-hour audio recording session on the third S7 ended up only reducing the crackles overall. They remained absent for more than 24 hours but then reappeared with reduced intensity. However, because the crackling has in fact never returned on my own S7 and S7 Edge after my video recording burn-in sessions, on Monday I decided to perform a one-hour video recording session on the third S7, too. And I'm happy to report that since that session the crackles have been entirely nonexistent on that device as well. If they return on any of the three S7 devices, I'll report back. If they don't return, the indication will be that a one-hour video recording session seems necessary to fully resolve the crackling issue.
I'm unsure why the audio recording session turned out to be unsuccessful on the third S7 device. I would think that an extended audio-only recording session should do the same thing with microphone input that an extended video recording session would do. But perhaps the extra heat generated during a video recording session is an important factor.
Click to expand...
Click to collapse
so I tried the audio method
basicly same results as ures started doing it again but a lot less so last nite I run the record on vga for almost 3 hours while I slept
and as of rite now clean and clear
I noticed it the other day I was recording some sounds to make a ringtone and thought I had ther volumes up to high and no matter what I did still popping and little bits of hissings too
well I recored the same sounds today at a louder volume than before and crystal clear
so +1 on a sofar fix
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
now I wonder if a man take and ground the phone out to a good ground source ive got the alligator clips ground braclets or something similar to discharge it instead of recording it.
TheMadScientist420 said:
so I tried the audio method
basicly same results as ures started doing it again but a lot less so last nite I run the record on vga for almost 3 hours while I slept
and as of rite now clean and clear
I noticed it the other day I was recording some sounds to make a ringtone and thought I had ther volumes up to high and no matter what I did still popping and little bits of hissings too
well I recored the same sounds today at a louder volume than before and crystal clear
so +1 on a sofar fix
Click to expand...
Click to collapse
Congrats! I hope it's permanently fixed for you.
TheMadScientist420 said:
now I wonder if a man take and ground the phone out to a good ground source ive got the alligator clips ground braclets or something similar to discharge it instead of recording it.
Click to expand...
Click to collapse
As for your discharge to earth ground idea... you can try it. But the circuit/component that's retaining the static charge may be isolated from the phone's chassis, so it may not work. The three S7s here still seem entirely free from the crackling. While I'm not entirely convinced that a few pops won't return at some point, I bet if they do they will be very few and that just one more burn-in session may eliminate them completely. But they also may truly be gone for good now.
My current theory is that the electrostatic charge some of these phones possess right 'out of the box' is great enough that it must be bled down in progressive increments. Whereas a few of the phones (like my two and my friend's) have less of a static charge initially, so they only require one burn-in session to completely bleed it away. As such, on the ones with a greater charge it may require several longer burn-in sessions to get rid of it entirely. That's at least my guess at this point. But, again, the three S7s here are still entirely clear of the crackles after only one FHD 1-hour recording burn-in session each.
clonk said:
Congrats! I hope it's permanently fixed for you.
As for your discharge to earth ground idea... you can try it. But the circuit/component that's retaining the static charge may be isolated from the phone's chassis, so it may not work. The three S7s here still seem entirely free from the crackling. While I'm not entirely convinced that a few pops won't return at some point, I bet if they do they will be very few and that just one more burn-in session may eliminate them completely. But they also may truly be gone for good now.
My current theory is that the electrostatic charge some of these phones possess right 'out of the box' is great enough that it must be bled down in progressive increments. Whereas a few of the phones (like my two and my friend's) have less of a static charge initially, so they only require one burn-in session to completely bleed it away. As such, on the ones with a greater charge it may require several longer burn-in sessions to get rid of it entirely. That's at least my guess at this point. But, again, the three S7s here are still entirely clear of the crackles after only one FHD 1-hour recording burn-in session each.
Click to expand...
Click to collapse
well make it 4 now
well I'm new to the s7 had s6 got a s5 and I was raising hell about some of the quality issues with the 7
no ir port downgraded camera downgraded processor I can deal with maybe not the ir port but the rest but I do a lot of videos and sound recs and like I said I thought input volume was just to much and thought it had crappy mics but sounds wonderful all day now.
TheMadScientist420 said:
well make it 4 now
well I'm new to the s7 had s6 got a s5 and I was raising hell about some of the quality issues with the 7
no ir port downgraded camera downgraded processor I can deal with maybe not the ir port but the rest but I do a lot of videos and sound recs and like I said I thought input volume was just to much and thought it had crappy mics but sounds wonderful all day now.
Click to expand...
Click to collapse
I'm happy to hear it! I've been very much hoping this may help a lot of people. I know how frustrated I felt after learning that both of my brand-new S7s, purchased six months apart from different sources, demonstrated the mic input crackling. I think what bothers me the most is that my research has shown this to be an unresolved, unaddressed issue affecting many Galaxy S devices since at least the S4 was current. It really upsets me that reports indicate everyone who calls Samsung tech support concerning the matter (including myself) is told by the support staff that they have never heard of the issue before - they've been telling folks that ever since the S4. One thing about such a response to a long-standing issue like this is that it means they have no idea what's causing it --because they've obviously not dedicated any time to troubleshooting it-- which also means they will most likely be unable to repair the devices sent in under warranty to fix the problem. I can't easily forgive Samsung for ignoring this issue, and I certainly will never forgive them for disavowing knowledge of its existence over the years to their paying customers who seek help from their support department.
I'll be anxious to find out whether, with persistence, this technique ultimately works on the most stubborn of crackling S7s.
clonk said:
I'm happy to hear it! I've been very much hoping this may help a lot of people. I know how frustrated I felt after learning that both of my brand-new S7s, purchased six months apart from different sources, demonstrated the mic input crackling. I think what bothers me the most is that my research has shown this to be an unresolved, unaddressed issue affecting many Galaxy S devices since at least the S4 was current. It really upsets me that reports indicate everyone who calls Samsung tech support concerning the matter (including myself) is told by the support staff that they have never heard of the issue before - they've been telling folks that ever since the S4. One thing about such a response to a long-standing issue like this is that it means they have no idea what's causing it --because they've obviously not dedicated any time to troubleshooting it-- which also means they will most likely be unable to repair the devices sent in under warranty to fix the problem. I can't easily forgive Samsung for ignoring this issue, and I certainly will never forgive them for disavowing knowledge of its existence over the years to their paying customers who seek help from their support department.
I'll be anxious to find out whether, with persistence, this technique ultimately works on the most stubborn of crackling S7s.
Click to expand...
Click to collapse
my primary device now for a long time has been a lgg4 and some people know about the bootloop issue
mines never suffered but I kow loads of people that have and a lot of them that have dealt with lg in the beginning and some still
they try to play it off like it don't exist
a well documented manifacs design flaw and I'm pretty foregiving when it comes to some of it I didn't turn away from Sammy for blowin up some batts hey it happens but they also swiftly did something about it
lg denied it for months before even thinking of replacing the hand set and still argue over it even though the device should've been recalled.
and I see people saying the g5 killed lgs sales it started with the locked bootloaders and bootloop issuses they wearnt adressing
TheMadScientist420 said:
my primary device now for a long time has been a lgg4 and some people know about the bootloop issue
mines never suffered but I kow loads of people that have and a lot of them that have dealt with lg in the beginning and some still
they try to play it off like it don't exist
a well documented manifacs design flaw and I'm pretty foregiving when it comes to some of it I didn't turn away from Sammy for blowin up some batts hey it happens but they also swiftly did something about it
lg denied it for months before even thinking of replacing the hand set and still argue over it even though the device should've been recalled.
and I see people saying the g5 killed lgs sales it started with the locked bootloaders and bootloop issuses they wearnt adressing
Click to expand...
Click to collapse
Well, the exploding batteries were quite dangerous... Samsung was forced to address the issue. As for the other issues, I think some companies (like Samsung) get away with selling flawed devices for premium prices. And that's disturbing to me. In my opinion, Samsung needs to implement better quality control practices. Ignoring an engineering flaw for 3 years while collecting significant profits on sales of the flawed products seems rather reprehensible.
I just did another 1 hour 30 minute recording session. This time the videos were cut into 3 parts, but I do notice significantly less popping when I tested a new video. Before I would have about four or five pops and static noises in the beginning. But I only got one so far. I'll continue to burn in to see if it improves.
Thanks
_LANTERN said:
I just did another 1 hour 30 minute recording session. This time the videos were cut into 3 parts, but I do notice significantly less popping when I tested a new video. Before I would have about four or five pops and static noises in the beginning. But I only got one so far. I'll continue to burn in to see if it improves.
Thanks
Click to expand...
Click to collapse
I'm glad you're finally noticing some improvement. Please keep us posted.
The static is back unfortunately. I'll get my usual 5 or 6 popping noises in the beginning of the video again even after 3 burn in sessions. I'm almost out of hope and so close to giving up lol
_LANTERN said:
The static is back unfortunately. I'll get my usual 5 or 6 popping noises in the beginning of the video again even after 3 burn in sessions. I'm almost out of hope and so close to giving up lol
Click to expand...
Click to collapse
Wow, that's terribly disappointing. And it's hard to understand since the three S7s here are still fully clear of the popping. This mic input crackling issue is certainly a bizarre problem. I'm very sorry that your device has not responded to the sessions the way several others have. It seems to work on some S7s but not others.
I know that you've already tried this method extensively. But in case you decide to perform additional sessions and things happen to change for the better, please let us know.
Well, it has been one month since I performed the burn-in sessions and I'm happy to report that all is still perfect. Neither my S7 nor may S7 edge have exhibited any popping or crackling artifacts whatsoever during video or audio playbacks. My friend's S7 also seems to be fully cured of the issue. Based upon these results I have to suspect that this procedure should work on any S7 (edge or non-edge) suffering from the same issue. Some devices may simply require a number of subsequent sessions to bleed away all of the electrostatic energy. Unfortunately, a few here and there seem to have retained a greater static charge than others. I think persistence may be the key.
Thanks for this tip!
Thank you very much, clonk, for this valuable tip!
I had the crackling since the beginning of my new S7. Yesterday I made a 1 and 1/4 hour continuous video and voilà, the crackling disappeared.
Repeated the test this morning in cold state serveral times - and except from one (!) single click sound no more crackling!!!!
I agree with your explanation of how this might come.
My additional assumption: electronics do wear and by this marathon video session tiny deviations in insulation material of the serial production may have been ironed out.
Maybe this insulation was too high so that static voltage could rise and discharge in a crackling signal.
And I cannot understand why Samsung does not (want to) know about this simple cure, either!
THANK YOU, THANK YOU, clonk!!!
Don't see how recording for 1 hour + would do anything whatsoever for electrostatic discharge, discharging yourself on a grounded point and then touching the metal chassis of the phone would discharge anything build up in the phone - and you picking up the phone while charged again would put it back, so....
Unlikely to be anything to do with static, much more likely to do with storage or software
xda-fritz said:
Thank you very much, clonk, for this valuable tip!
I had the crackling since the beginning of my new S7. Yesterday I made a 1 and 1/4 hour continuous video and voilà, the crackling disappeared.
Repeated the test this morning in cold state serveral times - and except from one (!) single click sound no more crackling!!!!
I agree with your explanation of how this might come.
My additional assumption: electronics do wear and by this marathon video session tiny deviations in insulation material of the serial production may have been ironed out.
Maybe this insulation was too high so that static voltage could rise and discharge in a crackling signal.
And I cannot understand why Samsung does not (want to) know about this simple cure, either!
THANK YOU, THANK YOU, clonk!!!
Click to expand...
Click to collapse
You're very welcome, xda-fritz. Glad to help. My two S7s (one is an edge) and another that my friend owns are still entirely crackle free. One of them took several sessions to fully eliminate the crackling. But it's been several months and the crackling has not returned on any of the three devices. So the process has definitely worked in our case.
*Detection* said:
Don't see how recording for 1 hour + would do anything whatsoever for electrostatic discharge, discharging yourself on a grounded point and then touching the metal chassis of the phone would discharge anything build up in the phone - and you picking up the phone while charged again would put it back, so....
Unlikely to be anything to do with static, much more likely to do with storage or software
Click to expand...
Click to collapse
If the electrostatic potential is present on a component or within a circuit that's normally isolated from the chassis, reasonably it would not have a path to ground through the chassis. That may change once the device toggles to record mode (via electronic switching within the circuitry). All I can tell you for certain is that the extended video recording sessions have resulted in huge reductions in, and often elimination of the cracking for multiple S7 users. In my case, the result has been complete elimination of the crackling on three S7 devices here (the two I own and one that my friend owns). We can speculate and/or argue about why that's so... But I have to tell you, Detection, the important thing is that it IS so.
Well whatever fixed it, I am certain it is nothing to do with static discharge, much more likely that the camera app / file it writes during recording is creating some temp file on storage that helps, or just coincidence
Recording or not recording will have 0 impact on electrostatic discharge
So, I'm currently sporting a Moto G5S+ with an Android 8.1 custom ROM applied to it, which has recently begun expressing behaviours with the audio that I have previously experienced on other devices both on the lower and higher end of the market. I've come to expect this, though it does disappoint me as a whole, and I believe it's something hardware-related, considering the symptoms. Since I noticed that this device was beginning to do the same as my other devices, I decided to bring it up here for discussion, and see if anyone else has had this issue.
When I first got this device, I was able to listen to my music, getting a full blast unlocked volume on par with my laptop. About two or three months ago I finally broke down to the then lack of updates past Android 7.1.1 from Lenovo, and installed the ResurrectionRemix 8.1 rom I found on the device forum following a standard bootloader unlock. Nothing changed then, at least not noticeably, until about two weeks ago, when I noticed that I was turning my volume up to max, and it was barely outputting enough volume to fully immerse me in whatever video or song I was watching or listening to. Again, this has happened to all the android devices that I've used as a daily piece for any length of time, and I'm not surprised that this phone exhibits the same behaviours after something close to a year of use. I don't know if there is some sort of resistor or capacitor I'm frying internally due to high volume use of the audio chipset, or if the Android software has decided that I'm listening too loud too long, and is decreasing the volume in software, outside of the volume slider, unknown to the user. If anyone else has had this experience, post your phone and how long you used it before it happened, or even if you didn't let's discuss this together. I'd like to get some second opinions and some friendly conversation about it.
yackaro said:
So, I'm currently sporting a Moto G5S+ with an Android 8.1 custom ROM applied to it, which has recently begun expressing behaviours with the audio that I have previously experienced on other devices both on the lower and higher end of the market. I've come to expect this, though it does disappoint me as a whole, and I believe it's something hardware-related, considering the symptoms. Since I noticed that this device was beginning to do the same as my other devices, I decided to bring it up here for discussion, and see if anyone else has had this issue.
When I first got this device, I was able to listen to my music, getting a full blast unlocked volume on par with my laptop. About two or three months ago I finally broke down to the then lack of updates past Android 7.1.1 from Lenovo, and installed the ResurrectionRemix 8.1 rom I found on the device forum following a standard bootloader unlock. Nothing changed then, at least not noticeably, until about two weeks ago, when I noticed that I was turning my volume up to max, and it was barely outputting enough volume to fully immerse me in whatever video or song I was watching or listening to. Again, this has happened to all the android devices that I've used as a daily piece for any length of time, and I'm not surprised that this phone exhibits the same behaviours after something close to a year of use. I don't know if there is some sort of resistor or capacitor I'm frying internally due to high volume use of the audio chipset, or if the Android software has decided that I'm listening too loud too long, and is decreasing the volume in software, outside of the volume slider, unknown to the user. If anyone else has had this experience, post your phone and how long you used it before it happened, or even if you didn't let's discuss this together. I'd like to get some second opinions and some friendly conversation about it.
Click to expand...
Click to collapse
If you're listening to your devices on max audio with any modified software than obviously you will induce some damage to components that are sensitive such as a speaker. Sometimes source codes can be incorrectly configured thus increasing the risk of damage to sensitive components. Manufacturers obviously test their software and devices for the degradation over time. But it's with their own software that's configured to their standard. Don't forget over time dust and gunk may build up on components hindering their fiction properly. Android won't scale down volume because it detects damage. It will use full blast 24/7 if that's what you set it to. If you are a smoker of cigarettes/tobacco then you will probably build up tar on speaker and microphone. There are quiet a few reasons as to what you maybe experiencing
I'm sorry in advance if my reply comes off as nieve and inflexible, I want to get down to what actually might be going on and I can tell you what isn't.
with any modified software than obviously you will induce some damage
Click to expand...
Click to collapse
I do not use any EQ or Volume enhancing software outside of the custom rom, and volume was identical between the ROM and stock. And two of my previous devices that experienced this problem (ZTE Max Duo, LG Stylo) were not even rootable. All volume never exceeded phone specifications and yet the audio chip lost volume over time on those, and I highly doubt it exceeded specifications on my G5S+.
If you are a smoker of cigarettes/tobacco then you will probably build up tar
Click to expand...
Click to collapse
I will stop you there, I don't commit upon that sin. And if there was some sort of buildup on my headphones, wouldn't that affect the laptop's output to them as well? Other than that I keep my phone, while not quite meticulously clean, decently sanitary, and I can say for sure that the grilles of the earpiece and bottom speaker are not clogged.
A good start, for sure. Just gotta keep digging.