Database Info

List of all the known G2x issues?

I currently have a Vibrant and I feel like this phone was a total POS until almost 6month later when voodoo lag fix came along and ROMS started to come out that had working GPS, better data, etc etc... If not for the dev community I would have thrown this thing out the window the 2nd time the GPS couldn't find me on google maps...
I love tinkering with a phone, but I also want to start with a phone that doesn't have random reboots, crappy GPS, slow file system lag and all the other crap I had to deal with the Vibrant (and my first android MyTouch 3g)... Althought most issues have been ironed out now, it took almost a year since I first purchased my Vibrant, and I am looking to upgrade either to G2x, Sensation or GSII. Don't want to start a battle which is better, but from what I gathered so far from G2x:
-Screen: hit or miss, some complain about bleed, some say its the best thing ever... seems like the quality control is really a hit or miss with the display
-Data: Won't connect to 4g network, generally seems to be unreliable and signal strength weaker than most phones but has a great GPS
-Battery: Heard there is a battery drain issue, some say its corrected with factory reset?
-Integration: Stock android 2.2? So I am guessing contacts aren't linked together to social network profiles?
-Build Quality: Better than most other phones, rock solid not many complain
-Speed: Looks like its a pretty quick phone for running on an un-optimized OS, will get quicker with updates
Before anyone starts praising and telling me this phones potential and that CM is going to make this awesome, I really don't care... my Vibrant had the potential to not be a total POS either, a year later its somewhat tolerable and right about the time when dual core phones have come out and me starting to look for upgrade. So I guess I just want to know what are some known issues with the phone today that you guys have noticed. I know there is no perfect phone, but I want something that can be tolerable for at least a little while before a custom rom comes out that doesn't breaks more things than it fixes

Me Personnally
I too also came from the vibrants ., and was also fed up with the crappy support from samsung, and that an official cm has still not seen the light of day.
Thats the reason i got the g2x. From what i heard, its completely open. Alot of the top devs for cm have or are getting the phone.
I think the screen bleed is something that everyone is going to have to get used too. I have some bleeds at the corner of my screen too.
Performance wise; without tweaks, just straight out of the box for me, this has destroyed my vibrant with teamweaskys latest rom.
I wont get the sensation because of the locked bootloader, and i am not going to trust or put up with the crap that samsung gave us with the vibrant.
This phone is AWESOME!!!!!!! i am loving it so much.
apart from the screen bleed, all the other issues you see here, are all temporary, i mean real temporary.
Ps
Saw a tweet come in with some peeps already running gingerbread on there gx2

Same Reason why I bought the phoen was because the bootloader is unlocked, but unfortunately this phone has to many other issue's.

timafey said:
-Screen: hit or miss, some complain about bleed, some say its the best thing ever... seems like the quality control is really a hit or miss with the display
-Data: Won't connect to 4g network, generally seems to be unreliable and signal strength weaker than most phones but has a great GPS
-Battery: Heard there is a battery drain issue, some say its corrected with factory reset?
-Integration: Stock android 2.2? So I am guessing contacts aren't linked together to social network profiles?
-Build Quality: Better than most other phones, rock solid not many complain
-Speed: Looks like its a pretty quick phone for running on an un-optimized OS, will get quicker with updates
Click to expand...
Click to collapse
These are my opinions.
-Screen: Yes, some bleed more than others. I think this issue has been blown way out of proportion as it seems the majority of users have to manipulate screen brightness, environment and content displayed on the screen in order to show bleed.
-Data: I only have 2G in my area. When I'm out in 4G areas away from home, I just set the connection to force 4G data and it's smokin' fast, never drops.
-GPS: Most of the time it locks on instantly for me on any Froyo ROM. Sometimes it takes about 60 seconds. If it looks like it's going to take a while, I usually close Maps, open GPS Status & Toolbox to refresh the AGPS data and it'll lock solid again. This should be fixed as soon as Gingerbread drivers are available.
-Battery: Battery is up to par with other Android phones in my opinion. Seems better on any tweaked out Froyo or Gingerbread ROM.
-Integration: I don't use social network/contact integration so I can't even touch on this. Don't know how and not interested. Sorry.
-Build Quality: Good weight, doesn't feel cheap. Generally accepted that it has Gorilla Glass. I have a couple extremely light scratches on my screen, so it's probably a good idea to get a screen protector if you care about such things. I just haven't touched a screen protector I like so I don't use one. I've taken the back off about 15 times and there is now one spot on the phone that if I squeeze, it creaks a little bit. Can't tell with normal use and still feels solid.
-Speed: Stock ROM is a little sluggish but with a couple flashable mods, maybe a kernel, this phone is super fast. I don't even feel the need to overclock. Currently running EaglesBlood Froyo 1.05 with faux's froyo kernel at the time of this writing.
Hope some of this helps you out.
Edit: And with an unlocked bootloader, just flash recovery and start crackflashing away. Love not messing with bootloaders.

Add Randomly REFORMATS to the list. My phone has reformatted itself randomly three times now since i've had it. stock. Once it like forgot it had an OS and just kept looping itself and then installed the OS randomly. Badass phone.

MavrcK145 said:
Add Randomly REFORMATS to the list. My phone has reformatted itself randomly three times now since i've had it. stock. Once it like forgot it had an OS and just kept looping itself and then installed the OS randomly. Badass phone.
Click to expand...
Click to collapse
I can atest this also has happened to me. LG has a class action suit against them, you should all file your complaints.

I made a thread about this because it could give insight as to whether there are deeper hardware issues that could lead to some of these software instabilities;
The 3.5 mm audio jack has very audible noise/hiss on it when the amplifier is turned on (up to 1 second after any sound finishes playing, such as after the tone you hear when changing the ringer volume). This should be completely inaudible if the circuit itself is designed properly and everything is shielded where it should be, and if the components related to power supply/filtering are working properly. If someone could test this (takes 5 seconds) with their good and faulty phones, stock or modded, it may demonstrate something.
More: non-reboot bugs. On pressing the power button to unlock the phone today (3 days since factory reset, 1.5 weeks since buying) the unlock slider is missing, except for the white triangle pointing to the right. Sliding it makes it appear and play the animation, and it appears next unlock.
Another random: Holding volume down until it is vibrating non-stop and then powering down the phone causes some apps to show and do random things after the power down animation plays, before the screen suddenly blanks.
I still urge owners of variably configured G2x's to test for the presence of noise as described in my thread- if LG has hardware problems instead of all software, not everything is safe by modding the ROM. Perhaps the noise is shoddy software coding. The DAC and opamps used here would not create that, only the circuit design.

k00zk0 said:
I made a thread about this because it could give insight as to whether there are deeper hardware issues that could lead to some of these software instabilities;
The 3.5 mm audio jack has very audible noise/hiss on it when the amplifier is turned on (up to 1 second after any sound finishes playing, such as after the tone you hear when changing the ringer volume). This should be completely inaudible if the circuit itself is designed properly and everything is shielded where it should be, and if the components related to power supply/filtering are working properly. If someone could test this (takes 5 seconds) with their good and faulty phones, stock or modded, it may demonstrate something.
More: non-reboot bugs. On pressing the power button to unlock the phone today (3 days since factory reset, 1.5 weeks since buying) the unlock slider is missing, except for the white triangle pointing to the right. Sliding it makes it appear and play the animation, and it appears next unlock.
Another random: Holding volume down until it is vibrating non-stop and then powering down the phone causes some apps to show and do random things after the power down animation plays, before the screen suddenly blanks.
I still urge owners of variably configured G2x's to test for the presence of noise as described in my thread- if LG has hardware problems instead of all software, not everything is safe by modding the ROM. Perhaps the noise is shoddy software coding. The DAC and opamps used here would not create that, only the circuit design.
Click to expand...
Click to collapse
I don't even think I own a pair of headphones anymore... hahaha. I'll try this with a set of powered speakers as soon as my children let me.

Wow I was going to buy G2x. Can anybody answer about 4G data part who use it on regular basis? Is it really not reliable?
I was thinking of upgrading from HD2 to g2x mainly because of 4G and front camera, but if 4G is not properly working on this one, I have to select some different phone then..

[Q] Extremely Low Call Volume - Is this a common problem?

Hi all.
Recently got myself my first smartphone, the Nexus S on Telus. (Well, had a Samsung Omnia before, but getting a WM6.1 phone in 2010 can hardly be considered smart )
Everything was going swimmingly. I have a penchant for changing up the software innards on the devices I own, so naturally I rooted my shiny new phone and had a good time trying out all these ROMS. This was approximately a month ago.
About a week ago my phone inexplicably began to act up. My in-call volume dropped to barely a whisper, and my touch-sensitive search button would for some reason go off on it's on.
After a bit of Googling, I found out that the search button issue is affecting many other Canadian users also, something about a bug in the new radio (AUCKD1).
But I've yet to find anything conclusive about the in-call volume. There are threads who are complaining of either low or high volumes, but no workable solutions.
So as a last resort I have restored my phone to fully stock 2.3.4. One to see if it was my messing around that caused it, and to also prepare for the possibility of having to return my shiny. It may just be my imagination/denial, but the call volume seems slightly better. Not good enough for me to hear outside, but inside, with no background noise it's just slightly quieter than normal.
Another thing that is very odd. Skype volume is much louder than voice calls. To be frank it's still not loud enough to be considered acceptable, but it is definitely louder. They use the same speakers right? Why would that be?
If at all possible I'd like to avoid having to take the phone back since Telus will no doubt charge me exuberant fees for having touched the phone for more than 3 seconds and moving more than 18 millimeters away from the store I bought it from.
Please advise, XDA!

U can try install kernel voodoo sound from supercurio and apps. U can see the different.
I had try most of the custom rom. There is one rom who give me loudest call volume, but I can't remember which ROM it is. U should explore more rather than bring it to the store.
Now I'm on liquidnexusbread, but not giving me a good volume in call.
I knew it sucks... but I love this rom performance.
Sent from my Nexus S I9020T

Real Solution for Recorded Audio Crackling (confirmed through testing)

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

[Help] Headset jack and 3-button Android headphone remotes

I picked up the AKG N20NC in-ears a few months ago, partially because the remote has a switch that makes it compatible with iOS (I have an iPad Air 2, be gentle) and Android (Tmobile Galaxy S7, stock and unrooted). But I found out a few weeks later that the + volume sometimes would actually lower the volume. AKG's Twitter support surmised it was a defective pair, so I returned it to the store & bought another a week or two later (serial number is only a few off from the first pair, d'oh) and still have the same problem. It's completely random and it will usually resolve itself after 30 seconds or so. I downloaded Android Remote Tester and can see that + sometimes is recognized as -. It then randomly rights itself, until the next time--whenever that is.
I'll deal with AKG Support again but I was wondering if anyone here had some technical insight into this issue. I know Apple uses (used) one configuration for the jack, and Android phones...use more than one. My Sennheiser Momentum Android models work flawlessly on my S7 , and I never had problems with the Xiaomi Pistons. So why would the AKGs have this sudden problem? I know 3-button Android remotes are rare, perhaps the different configurations is a reason why. I remember I had a Sennheiser active headphone for a bit and the remote didn't work with my LG G2, despite being labeled for Android.
I really want to keep these so I have a pair of NCs to use in warmer weather and for when I don't want to carry around my Momentum 2 AEBTs.

WheresTrent said:
I picked up the AKG N20NC in-ears a few months ago, partially because the remote has a switch that makes it compatible with iOS (I have an iPad Air 2, be gentle) and Android (Tmobile Galaxy S7, stock and unrooted). But I found out a few weeks later that the + volume sometimes would actually lower the volume. AKG's Twitter support surmised it was a defective pair, so I returned it to the store & bought another a week or two later (serial number is only a few off from the first pair, d'oh) and still have the same problem. It's completely random and it will usually resolve itself after 30 seconds or so. I downloaded Android Remote Tester and can see that + sometimes is recognized as -. It then randomly rights itself, until the next time--whenever that is.
I'll deal with AKG Support again but I was wondering if anyone here had some technical insight into this issue. I know Apple uses (used) one configuration for the jack, and Android phones...use more than one. My Sennheiser Momentum Android models work flawlessly on my S7 , and I never had problems with the Xiaomi Pistons. So why would the AKGs have this sudden problem? I know 3-button Android remotes are rare, perhaps the different configurations is a reason why. I remember I had a Sennheiser active headphone for a bit and the remote didn't work with my LG G2, despite being labeled for Android.
I really want to keep these so I have a pair of NCs to use in warmer weather and for when I don't want to carry around my Momentum 2 AEBTs.
Click to expand...
Click to collapse
Seems like it's a hardware flaw in the volume rocker/switch. I've experienced this, usually because the rocker/switch is poorly designed such that, for example, when you press volume +, the components in the switch actuate in a manner that it actually presses the volume -.
I've noticed on some of these types of rockers/switches, if you carefully press at the extreme ends of the rocker/switch, it registers correctly. Placing your finger on the center of the rocker/switch and pressing one way or the other can actually accidently place the pressure on the wrong side of the rocker/switch that what you intended.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Seems like it's a hardware flaw in the volume rocker/switch. I've experienced this, usually because the rocker/switch is poorly designed such that, for example, when you press volume +, the components in the switch actuate in a manner that it actually presses the volume -.
I've noticed on some of these types of rockers/switches, if you carefully press at the extreme ends of the rocker/switch, it registers correctly. Placing your finger on the center of the rocker/switch and pressing one way or the other can actually accidently place the pressure on the wrong side of the rocker/switch that what you intended.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
That's something I was messing around with while I was in Android Headset Tester, and IIRC, even the extreme top end of the + button would still be interpreted as a - press. The issue will go away after maybe 30 seconds, and no telling when or if it will come back. Also odd that a - press wouldn't then be interpreted as a + press, I've tried the minus button whenever this issue pops up and it always works as intended. It's just Up volume.

WheresTrent said:
That's something I was messing around with while I was in Android Headset Tester, and IIRC, even the extreme top end of the + button would still be interpreted as a - press. The issue will go away after maybe 30 seconds, and no telling when or if it will come back. Also odd that a - press wouldn't then be interpreted as a + press, I've tried the minus button whenever this issue pops up and it always works as intended. It's just Up volume.
Click to expand...
Click to collapse
It would be hard for me to imagine it being a software thing so it has to be an issue with hardware. How or why is another question.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Android 12...bugs so far?

I noticed the OXYGEN UPDATER APP now has Android 12 available to install but it hasn't quite made it to the official update in the settings. Just wondering if anyone has tried this update and whether you experienced or heard of any bugs?
I have no reason to think there is but Ive literally heard nothing good, bad or neutral. It's like no one owns this phone anymore. An update like this used to be noteworthy. That said, if anyone reads this and you have info, please share. Thanks

I have updated my device today and one thing I have noticed the most is that volume levels after the update are much lower than they were. I cannot use normally my earphones indoors and cannot image how bad it will perform outdoors.
Would be grateful if someone knows how to fix such problem.

uacyber said:
I have updated my device today and one thing I have noticed the most is that volume levels after the update are much lower than they were. I cannot use normally my earphones indoors and cannot image how bad it will perform outdoors.
Would be grateful if someone knows how to fix such problem.
Click to expand...
Click to collapse
I appreciate the feedback. I still haven't updated, but lately I've had volume issues. Both pairs of ear buds are noticeably lower than they were in the past. On one pair the right ear bud is barely usable, especially in a somehat noisy setting, but it's gotta be an issue with the ear bud.
In general, I need to crank them all the way up in the gym.

KLit75 said:
I appreciate the feedback. I still haven't updated, but lately I've had volume issues. Both pairs of ear buds are noticeably lower than they were in the past. On one pair the right ear bud is barely usable, especially in a somehat noisy setting, but it's gotta be an issue with the ear bud.
In general, I need to crank them all the way up in the gym.
Click to expand...
Click to collapse
I have fixed the issue with low sound levels when using earphones, but, unfortunately, I cannot describe clearly how 'cause it was a bit incomprehensible. I just connected one more time my earphones to smartphone, opened some video on YouTube, then pop-out of some option about volume came out. Then I tapped on it and there was an option that has strange description (maybe it is because of localization) that I switched on, and the volume issue fixed magically. After that, I couldn't find that option once again in settings.

Sounds familiar. I think it's a built-in volume limiter. Should be able to find something in the settings and if not maybe enable developer settings and see if you find it there. Something like "absolute volume".
But it looks like you got it sorted out anyway.

Actually nevermind. I got that confused with something else. I believe all that would do is keep the earbuds and the phone volumes separate.

There's been talk that Android 12 and Android Auto don't work well in some cars - not OnePlus specific, but in general. Has anyone tried Android Auto with 12 yet on the OP8?
Alan

I did the update, and here is what I notice:
The icons on top of the screen are not the same size.
The Notifications sometimes are lost (Whatsapp/text etc)
Whatsapp voice calls echo and sometimes the phone does not ring
Ghost touches when gaming (clash royale)
The screen goes ON for no reason
The battery sometimes is okay, sometimes it drains (your mileage may vary)
Screen unlock fingerprint behavior slow at times and sometimes is fine.
The volume issue that everyone is reporting
All of if has been reported to OnePlus. If you visit the OP forums everyone is pretty pissed off about it myself included.
Honestly, it feels like this is an Alpha version of the ROM and they are using the general public to test and find bugs.
This is pretty frustrating a phone is not a toy is a tool for work and to communicate with others.

Fingerprint unlock stops working after a few days. Reboot brings it back.

Just to update. AA works fine with Android 12 on my OP8