Related
I've seen a few hit or miss issues that have been coming to light since the release of the TF700 infinity. On some devices, it seems to work and on others, not as well or not at all. From this, it seemed quite necessary to have a thread to identify the issues that others may encounter and for what they should check to know if they have a "good device" or whether it should be returned. Please let me know if their are any items that should be related to this list. If you wish to discuss your tablet's attributes (both good and bad) further, Pretoriano80 has made such a thread: [Infinity issues/defects/good features] Share your issues, defects or best features
Make sure you charge your tablet before using! Explanation in point 3.
Also, do not update past 9.4.5.26 during these tests if you want to use NVFlash!
1- Does your device have good build quality?
Some people have found that there are scratches on the device, frame's bent, the display is poorly set, the ports may be improperly mounted or other such things. It is recommended that if you encounter any of these that you return the device to get another one since you paid a lot of money for a "good" device. The tablet might click at corners, some of the backlight might bleed through around the edges of the display, or maybe show a slight but often not serious protrusion of the screen from the device. It's up to you to judge whether the extremity of this occurrence on your device are serious enough to warrant a return depending on your definition of "quality".
A possible test for "light bleed" is to take a picture from the camera in either a dark room or the camera lens covered (objective is to take a "black" photo). Open the image in the gallery app and turn up the brightness on the device. In this fashion you should be able to notice any "severe" cases of light bleed like this. If the light bleed is little and only noticeable during startup, then it's probably nothing to worry about.
2- Does your device have haptic feedback? (Does it vibrate properly?)
When you turn on and off your device, it should vibrate. This vibration will be subtle like the feeling of a working electrical appliance and not like a console joystick. If it doesn't, then it probably is defective. There are various methods to getting some type of jiggle out of the tablet if you want a more extensive test. One example is to add such feedback to your on-screen keyboard via Settings -> Language & Input. I'll just go over the basic "Android Keyboard". Select the sliders button next to the keyboard, look for "vibrate on keypress", put a little check next to that, then go into "advanced settings". By default, these vibrations are set to 1ms which is a duration too short to provide any feedback. Adjust the "Keypress vibration duration settings" to something like 100ms in order to ensure that the buzz happens. Finally, verify that your default keyboard is set to the "Android Keyboard" and then open up something like SuperNote where you can type. You should have some buzzing upon every keypress. When done with this test, just go back into the keyboard settings and disable the "vibrate on keypress".
3- Is your battery life ~9 hours in power-saving mode or ~6 hours in balanced mode?
Some people have noticed that they either never reach this amount or never come close to it. This is kind of an expected behavior since on the first page of the instructions manual (you did read the manual, right?) it mentions this:
"Fully charge the battery up to eight hours for the first-time use. The battery reaches its maximum capacity after one full charging and discharging cycle." Therefore, one is supposed to charge the battery for up to an 8 hour period prior to use and then discharge the battery (until ~10% or so). You may encounter a variant of this concerning "a few cycles" but still, right after tearing the plastic off the box like a rapid child at Christmas, ensure that you just plug it in and forget about it for 8 hours (or until the charging light turns off). Otherwise, it can have a lasting negative impact on battery life.
More information about Li-ion can be found here.
4- Does the GPS work?
The TF700 shares a few things with the TF201 Prime (which had notoriously bad wireless, including Wifi communication, Bluetooth, and GPS). Some owners of the Prime didn't remember to check GPS even when everything else worked and later needed to get a Dongle. Ergo, why I put it here high on the list. I believe many of the issues dealing with hardware and software have been addressed by ASUS so if your GPS doesn't work, try updating (not past 9.4.5.26!) the device or send it back since it might be hardware related. Make sure that when testing, you have the "find location via wifi" option turned off if using Maps. Otherwise, test with a tool from Google Play Store like GPS Status or GPS Test. Note: testing may involve going outside and dancing with the device as the first connection is often the most difficult to get.
When GPS is working, you should see a little circle with a blinking dot inside in the lower right-hand corner. Sometimes, the dot might not blink and can seem to influence how well GPS programs work. Its a strange thing but with a simple solution (from myself encountering it on both the TF300 and the TF700): just open the notifications bar and close it again. The dot should be blinking. If not, try actually turning off and then turning back on the GPS via the notifications bar.
5- Does mini-HDMI work?
Though not necessarily a tendency of faults in the infinity, it is important to check all the offered functionality of the device prior to making it a permanent fixture in your life. Remember that if you don't have a friend with a mini-HDMI cable, Walmart (and many other stores) will accept returns provided they are within a particular time period. Feel free to use this return policy to test your device.
6- Can you watch video/youtube/netflix/etc while using a bluetooth headset?
Some people have noticed that there is a huge decrease in speed when watching a video while using a bluetooth headset for audio. The cause of this is unknown and the only explanation we know of is "because wifi and bluetooth share the same antenna". This seems plausible except that many other devices also use the same antenna for both functionalities yet do not display this behavior. Due to the underlying fact we do not know whether it is software or hardware related, it is advisable to return the product.
7- Does the headphone jack work?
Just for thoroughness and ease-of-testing, plug in a set of ear buds and make sure you hear sound. Some have complained that the quality is mediocre due to a humming noise but that the noise is negligible. If the noise is too pronounced, there still is the mounted speaker and if point 6's test was successful, bluetooth is still an option.
8- Does your device feel quick to respond? If not, are you on firmware version .26?
It has been widely noted that version .26 of the firmware made the tablet very snappy. This also helped the device to recognize more microSD cards but also caused problems with NTFS-formatted drives. If you aren't getting the response you want, try upgrading to .26 (not beyond that). Additionally, if your microSD card is NTFS, you may want to reformat it (backup whatever you want to keep first) to FAT32 or exFAT until the issues with NTFS are ironed out. This point also concerns point 9 further down.
9- Can you receive OTA updates? (This should be fixed since Aug 7)
Provided that you are on version .21 or .22, you should be able to receive updates from ASUS for your device via the "About Tablet" option in settings. If you cannot, this might be indicative of another issue which has yet to be identified. You can apply updates without OTA via these methods:
(easiest way)[HOW TO]Tired to wait the .26 with WW TF700 device?
(another way)*** Firmware News & Alternative Install Methods*** Ver. 9.4.5.26 27/07
(requires root)[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server
(requires unlocked bootloader)[HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Bootloader
(requires unlocked bootloader and TWRP custom recovery)[CWM] Repackaged OTA update 9.4.5.26 US/WW versions
Make sure you do not update past 9.4.5.26 if you want to use NVFlash!
10- (Only if this is important to you and then only if you are willing to forego any ASUS warranty) Can you unlock the bootloader? (This should be fixed since Aug 7)
Bonus Warning: ASUS has noted that using their bootloader unlocker will void your warranty and all OTA updates for your device will cease. However, without this unlocking, you will not be able to run custom ROMs nor will you be able to use NVFlash to make your device brick-proof.
[Device is unlocked][Video Added] Bootloader Unlock Tool Released [25.7.2012]
If you are still within your store's "grace period", you may want to try this out to verify if your device will ever be able to run non-ASUS android systems. There's no way of knowing at this moment if the bootloader unlocker will work on your device without actually trying to unlock it. If it does not work, it might be due to their service being unavailable, your serial number might not yet be in their database of devices for the unlock to succeed, your device serial number internally might not match your external serial number (on the sticker), or the problem might be something else entirely. Many of those whose bootloader would not unlock did not receive OTAs either so this shares the "issue which has yet to be identified" from point 9.
If you can give your tab a :good: to all of these points, then you have a good device! Congratulations! :highfive:
Maybe check out these threads next:
[INDEX]-[Updated -25 July 2012]-ASUS INFINITY TF700 - INDEX THREAD-DEVELOPMENT-PART#1
[RESOURCES] How to Root, Unlock, ROMs, Recovery, Tips & more [VIDEO TUTORIALS]
1.Yes
2.Yes
3.Yes
4.didn't try that yet
5.yes
6.yes
7.I don't care
Sent from my GNexus
Yep, mines a keeper.
Build quality is acceptable .. (I own an ipad also) ...I'm going to say 80% the build quality of the ipad. It does OTA and manual updates just fine. Headphone jack works. Has slight click if you press the screen by the speaker ...but only noticable because I read here that it clicks if you press by the speaker . Speed, temps, light bleed, battery life ....all as expected ...not perfect but perfectly acceptable. I am enjoying the tablet, and have no major complaints. I can only assume it will get better with JB when it comes out.
The ipad is more polished, faster, easier to use ....but not by a huge margin. And I make allowance for the immaturity of android tablets and the OS compared to ipad and iOS. I think the trade off is worth it for the additional control... and eventual rooting of the device.
Price ....hmmmm... perhaps a bit high compared to the ipad.... about $75 less would have been nice ....but it's basically a toy for me so I can't complain too much. And part of the whole thing is I wanted a tablet....and I wanted to support the Android market so it would stand a better chance at competing with the ipad... because honestly I think Andriod is the future of tablets ...not iOS.
I'd say the single disappointment is ....I bought the tablet to watch motorcycle racing videos from MotoGP.com, which I pay about $120 US a year to be a member ..... guess what...the tablet will not play the archived videos from this site ....it will stream live video fine, it will play all other "current" content fine...but will not play the archived videos ...... my iPad plays them just fine. I'm in contact with MotoGP.com trying to solve the problem ...but it's not a new problem ....its across the Asus tablet line.
Still.... I enjoy the TF700T, and think it's a good product ....although perhaps should be offered at a bit more of a discount compared to the iPad ....for now.
I have no regrets.
JohnnyB
ray3andrei said:
1.Yes
2.Yes
3.Yes
4.didn't try that yet
5.yes
6.yes
7.I don't care
Sent from my GNexus
Click to expand...
Click to collapse
Just want to mention these numbers are apt to change due to new things becoming evident as community use increases.
dataway said:
I'd say the single disappointment is ....I bought the tablet to watch motorcycle racing videos from MotoGP.com, which I pay about $120 US a year to be a member ..... guess what...the tablet will not play the archived videos from this site ....it will stream live video fine, it will play all other "current" content fine...but will not play the archived videos ...... my iPad plays them just fine. I'm in contact with MotoGP.com trying to solve the problem ...but it's not a new problem ....its across the Asus tablet line.
Click to expand...
Click to collapse
This thread is really just supposed to be a developing checklist for people to verify their tablets since it seems that not all problems are experienced by all users and some problems are more extreme than others. That being noted, how did you try to access said videos? Is there a specific program or application you are required to use? Did you try other such programs from the Play store? Since you are paying for your access, I doubt it would be something that a non-member would be able to assist much.
Yes it is a keeper
Plays HD content flawlessly
The GPS is sooper dup on the road
The WIFI sensitivity is exceptional
Can be viewed outside easily
I really like the hotspot tethering performance also
Pretty much a sweet package
I use it a lot around the house to help me with DIY project info...
1- Does your device have good build quality?
10/10, clicks a a little but IDGTF.
2- Does the GPS work?
Yes.jfif
3- Does mini-HDMI work?
Never tested, never will.
4- Can you watch video/youtube/netflix/etc while using a bluetooth headset?
>2012
>bluetooth headphones
ISHYGDDT
5- Does the headphone jack work?
Yes, makes beeping rarely when I start videos.
6- Does your device feel quick to respond? If not, are you on firmware version .26?
Yes, like butter. I still want jelly Bean though.
7- Is your battery life ~9 hours in power-saving mode or ~6 hours in balanced mode?
6 hours in balanced, yes. Never go to power saving because lag.
8- Can you receive OTA updates?
No, bootloader unlocked.
9- (Only if this is important to you and then only if you are willing to forego any ASUS warranty) Can you unlock the bootloader?
Already did
The only issue I've really had with my device after upgrading to .26 is occasional lock-ups. One lock-up concerned me enough to feel a need to return the device. The screen filled with vertical (if holding landscape) white bars. Has anyone else experienced such issues?
I haven't tested the HDMI yet. And other then the inability to OTA or unlock everything is working perfectly on the latest build
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
funtapaz said:
The only issue I've really had with my device after upgrading to .26 is occasional lock-ups. One lock-up concerned me enough to feel a need to return the device. The screen filled with vertical (if holding landscape) white bars. Has anyone else experienced such issues?
Click to expand...
Click to collapse
My friend found one at Best Buy here in NJ. I told him to return it (not exchange) because of the amount of light bleed alone. He was not able to update it, and it just kept crashing on him which made it almost impossible to use. He's going to try hard reset it again to see if any of that helps.
1- Does your device have good build quality?
Mine is perfect.
2- Does the GPS work?
GPS so far works great without using the AGPS to assist.
3- Does mini-HDMI work?
Have a cable from my Prime, both worked flawlessly as does my Bionic.
4- Can you watch video/youtube/netflix/etc while using a bluetooth headset?
Funny thing it does drop from about 20 Mbps to about 3Mbps down, but that won't change no matter how far from the router. The upload is 4Mbps on both no matter how far from the router. It's not the dual antenna that's the problem, it's that they both use one controller chip for the two.
5- Does the headphone jack work?
No problems on mine.
6- Does your device feel quick to respond? If not, are you on firmware version .26?
Was definitely laggy on .21, on .26 MUCH better especially in performance mode. I'm excited for JB.
7- Is your battery life ~9 hours in power-saving mode or ~6 hours in balanced mode?
I charged about 4 hrs till green/fully charged. Funny thing is you can't overcharge these new batteries now and days. They are set to auto stop charging once full (that's the benefit of them now) So I have never "overcharged" because it's not possible. That being said I did a full charge, and am working on the first full depletion to recharge. I'm at 62% and that's 3 days later lol. I have been using it light/moderate the past few days. At least 3.5 hrs of Netflix streaming, setting it up, and not turning it off overnight. We'll see but so far so good and Ifinitely (like that ) better than my Prime.
8- Can you receive OTA updates?
Not OTA, manual worked just fine
Good list, thanks. Mine has passed all of these so far but the headphone test. I forgot that one. I guess I'll give it a shot tonight.
" "Fully charge the battery up to eight hours for the first-time use. The battery reaches its maximum capacity after one full charging and discharging cycle.""
It says" upto 8 hours" It doesn't mean you NEED the full 8 hours. Once you go green and are 100% fully charged, the charger shuts down on its own so not to overheat the battery. The "upto 8 hours" is for folks charging their device via USB on their PC - - which can take up to 8 hours to getting that full charge.
I just got mine yesterday, and while I haven't had time to test either HDMI or full battery cycle (though it's doing pretty well so far) all else is wonderful. Great screen, OTA update to build 26, great wifi and gps, headphones work fine. Sound out of headphones and BT headset is actually great. I do have a millisecond lag with BT audio and watching streaming video, but I could actually live with it, it's not that bad.
This one is definitely a keeper.
I have a quick question while I'm checking my tablet, which arrived yesterday... my screen is uniform across the edge, no creaking or inconsistencies, but the entire surface is raised, or at least isn't flush like my previous Prime. Is that normal? Anyone have a completely flushed screen on their 700? Thanks.
Sent from my Incredible 2 using xda app-developers app
androidxen said:
I have a quick question while I'm checking my tablet, which arrived yesterday... my screen is uniform across the edge, no creaking or inconsistencies, but the entire surface is raised, or at least isn't flush like my previous Prime. Is that normal? Anyone have a completely flushed screen on their 700? Thanks.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
My Gorilla glass has about a quarter inch beveled edge going all the way around
xRevilatioNx said:
My Gorilla glass has about a quarter inch beveled edge going all the way around
Click to expand...
Click to collapse
So I guess the screen is higher due to the hardware improvements from the Prime. Good to know, just wanted to be cautious.
Sent from my Incredible 2 using xda app-developers app
xRevilatioNx said:
My Gorilla glass has about a quarter inch beveled edge going all the way around
Click to expand...
Click to collapse
Same here - more like 1/16th inch, maybe?
Mine looks perfect, but if I press a bit harder on the screen (you won't do this with normal usage) I get a hissing noice which sound like air is escaping from between the screen. At that moment I can see deformations on the screen. I have read other people do have the same issue, but wondering if this is normal (so all TF700 have it?) or if I should exchange. Any advice?
I have one really big scratch on the dockingstation. Going back to the store tomorrow to get another one.
Added xRevilatioNx's and neo1738's clarification regarding initial battery charge and the green charging light turning off.
Yeah, I agree with you that the new batteries can't be overcharged in the literal sense. It was merely to emphasize the fact that a "full charge" is necessary to receive optimum life out of the device's battery. We don't really know what type of charge existed on the device prior to our receipt, so it's best (or in a worse case scenario) just to charge it for the 8 hours regardless of the status of the light. Does it make a difference if it's 8 hours or until the green light turns off? Probably not. But for the Android neophytes just getting their hands on a tablet for the 1st or 2nd time, I think that my explanation is still applicable and satisfactory to provide a perspective easy to understand and beneficial to the consumer. Thanks for the detailed clarification though.
Received my champagne gold today and doesn't seem to be any issues at all. No light bleed, WiFi and bluetooth are perfect, and no I/O issues (updated as soon as I turned on the device). Seeing as the champagne golds seem to have come latter in the production cycle, it seems they are improving their processes slowly but surely.
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
Every android phone I've ever had from 2011 to 2016, whether it be samsung or LG, has had the same problem. That problem is the inability to use the sound device in many circumstances for 2 operations at once. Primarily I am talking about recording the sound from a device at the same time as using an app such as whats app or skype. As soon as any audio recording app I have used begins to record in an attempt to record a call, the microphone seems to stop working and the other person on the call cannot hear you. The same problem occurs when trying to record a video at the same time as making an audio recording. A message simply comes up on screen with words to the effect of, "the sound device is already in use", or something similar. I know there are ways to record calls with apps using the normal phone functionality, but it seems more difficult with apps. Ideally any app should be able to use sound devices at the same time so you shouldn't HAVE to find a work around or a specialist app as that takes up precious brain juice and time and effort and life is just too short for that. It should just work by default easily. You wouldn't expect the audio card on your pc to stop recording audio just because you were recording output sound so why should things be any different with a phone?
I can't help feeling this very annoying problem should have been solved years ago without having to go in to potentially time consuming shennanigans to get around it, (assuming there is a way round it at all!). Lets explore some possible reasons for this..
Is this a software issue that can be resolved some way or another involving rooting etc?
Is it another example nanny state nonsense trying to stop what it thinks might be excessive use of resources? The kind of nanny state rubbish which plagues android and tech in general these days like a horrible disease in the name of artificial intelligence (albeit dumb and rudementary), or for the supposed purposes "improving" device experience or resource management when most of the time it makes the user experience far worse and far more stressful with it's interference, (e.g turning down the sound to 'protect' your ears when plugging in at 3.5 jack etc etc)
Or is it an actual hardware issue? i.e the hardware is just incapable of multiple uses at once...
If it is a hardware issue, then why on earth has this not been fixed by now? Or are there now phones that don't have this problem any more? Is it a case that the corporate scum who make these phones just don't see it as worthwhile to put in better hardware to make these uses possible? Because they care more about saving a few pennies than making a good product? Or because the dumbed down sheeple won't use such extra functionality? Or both?
If there are phones which no longer have this problem, which are they? Because I would like to avoid this with my next phone which I will be getting sooner rather than later. I don't think I can bear yet another faulty phone with this problem, as that is how I see it, or at the every least a deep design flaw. Is this a problem that effects tablets as well as phones?
If the only solution is a work around, what is the easiest and simplest work around if one is required that would work on a general basis rather than a case by case work around. Is there light at the end of the tunnel on this with future designs and developments so we don't need to have work arounds in the near future?
Thanks in advance for the thoughts and insights.
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.
i read here and elsewhere about some issues with this device, but i can't tell for sure if its common or just certain people who were unfortunate.. i have a few questions and i hope you guys could help..
1- is there a common issue with wifi and/or cellular(LTE, 4G, 3G) connectivity in this device, such as dropped calls, dropped signal, wifi misbehaving ?
2- is there a common issue regarding the stereo speakers? (some say people around could hear the person you're talking to on the phone, others say the phone vibrates when playing music!)..
3- is it possible to set the display refresh to say 60hz from settings, or does it change automatically and can't be controlled by the user?
4- are there any common issues with custom roms, for example custom roms for the note 8 pro all have issues with automatic brightness and maybe a few more things!!
5- is there anything else i should know or worry about regarding this model?
hope you guys could help. thank you.
jaikat said:
i read here and elsewhere about some issues with this device, but i can't tell for sure if its common or just certain people who were unfortunate.. i have a few questions and i hope you guys could help..
1- is there a common issue with wifi and/or cellular(LTE, 4G, 3G) connectivity in this device, such as dropped calls, dropped signal, wifi misbehaving ?
2- is there a common issue regarding the stereo speakers? (some say people around could hear the person you're talking to on the phone, others say the phone vibrates when playing music!)..
3- is it possible to set the display refresh to say 60hz from settings, or does it change automatically and can't be controlled by the user?
4- are there any common issues with custom roms, for example custom roms for the note 8 pro all have issues with automatic brightness and maybe a few more things!!
5- is there anything else i should know or worry about regarding this model?
hope you guys could help. thank you.
Click to expand...
Click to collapse
This phone is the most bang for your buck imo, but nothing is perfect, so to answer your questions:
Signal strength in this phone is absolutely great, especially the 4G+/LTE+ mode (if your carrier supports it). If i were to to compare Poco x3 to high end devices, I would compare it to a Samsung Note 9 or in the similar generation/production year. Some Custom ROMs have issues with 5GHz wifi reception, but on most of them and stock MIUI you will find no issues.
After MIUI 12.0.4.0 (currently 12.0.7.0 is latest) the speaker problem was resolved. It mostly was due to the fact that calles were handled in stereo mode instead of mono and the treble was too high, but It was noticed quickly and dealt with. Music will still rumble a bit in highest volume, although it gives the bass a better boost (people here have different opinions on this issue).
If you plan to use the phone at stock MIUI, you will get two refresh rate options: 60Hz and 120Hz, both of which are dynamically adjusted to the content you are on. For example youtube will scale down to 30Hz when watching a video regardless of which option you chose. Custom ROMs (all of them) have this feature/annoyance called displayfeature hal removed and have added a 90Hz mode as well. So a stock experience isn't advised.
Nothing notable comes to mind. Ok maybe Camera is slightly an issue, but Gcam is getting better everyday where it's almost the same as stock cam (if not better). If you divide different xda phone forums into alpha, beta and stable, then our phone has already transitioned from beta to stable status. You have missed the "beta" phase by a few months now.
Like all Xiaomi devices, EDL mode is locked. Meaning a hard brick is costly to fix/repair. If you never flashed a phone shipped with android 10 before (most people haven't), then read all instructions very carefully, especially recovery threads. Magisk CTS sometimes doesn't pass, but that issue isn't really exclusive to this device.
I have bought two devices. One early in September, which has no issues. The other I had to return recently due to QC issues, as it only had 85% battery capacity (from official seller), so my advice would be to check everything including sensors and battery. If everything looks ok, then you're all set.