yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] droid745:
On my Verizon LG G3 sometimes people I am talking to complain that it sounds like I am getting far away and then they can not hear me for a second before the audio for them comes back. When I researched this other people with the Verizon G3 have had this issue and I am wondering now that custom recovery can be flashed, will custom roms/kernals fix this issue? it seems like there is something off with the noise cancellation and that is why it cuts out if not held just the right way.
[Verizon LG G3] Bluerai:
Having the same issue, wondering the same thing.. Hope it'll 'get fixed' though.
[Verizon LG G3] blueis300:
I upgraded using the Best Buy method to keep my UDP. Anybody no if it ok now to then going into Best Buy and try to warranty the phone or go Into Verizon for a new sim card?
[Verizon LG G3] jfriend33:
What problems u having
[Verizon LG G3] cali4nia831:
Same problem here. Have found no solution so far...
[Verizon LG G3] tech_head:
Only started happening to me when they started rolling out VOLTE in my area.
[Verizon LG G3] JesseMT4G:
I have always had it. Drives me nuts, but it's just hear and there. More annoying than anything I guess. Figured coming from T-Mobile it would be better voice. Boy was I wrong....
[Verizon LG G3] rp201:
I disabled two items like call enhancement and background noise suppression or something like that and in call audio

issues went Away. I froze all vzw apps and lots of others and was thinking the combo may have been issue
[Verizon LG G3] CTNewb:
How were you able to do that?
[Verizon LG G3] rp201:
G3 tool box call call tweaks uncheck noise suppression

Sent from my VS985 4G

---------- Post added at 01:36 AM ---------- Previous post was at 01:34 AM ----------

Settings call call enhancement is unchecked

Sent from my VS985 4G
[Verizon LG G3] droid745:
I have voice enhancement unchecked but,I don't have an option for background noise suppression/cancellation. Is that an extra option that you need root to access? My solution for this issue is to sell my g3 and switch to a new phone.
[Verizon LG G3] droid745:
[6303156]I disabled two items like call enhancement and background noise suppression or something like that and in call audio

issues went Away. I froze all vzw apps and lots of others and was thinking the combo may have been issue[/QUOTE]

I might have to root my g3 and try this. My note 4 is getting delivered tomorrow but if this works for my phone I might have to return the note 4. Do you have problems on your calls now with background noise coming through making people you are talking to able to hear that noise easily now?
[Verizon LG G3] rp201:
G3 toolbox in play store. Not sure if that setting needs root. Not sure if you need xposed for g3 toolbox module. Not sure if you u need donation g3 toolbox. Sounds more like hardware defect....but I'm not a doctor. G3 lifer here.

---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------

I also found people saying same if I did not hold phone flat and tight to my face
[Verizon LG G3] droid745:
Well I was able to install g3 tweakbox without root and saw the noise cancellation item and it was unchecked already. Not sure if it was because I was not rooted and maybe if i root and install exposed that when I go in it would be checked off for noise cancellation so that I could then disable it.
[T-Mobile, Samsung Galaxy SIII] Scath:
Okay everyone here is a hard one...

My son cracked my screen on my S3. It works and functions I put a screen protector on it for now, don't ask why I haven't fixed it yet -- it's irrelevant.

A few nights ago I was sleeping and I woke up to my phone super hot, couldn't even hold it in my hands, but it was okay and was working fine I let it sit out overnight and cool off then charged it back up. All seemed fine, until a day or so ago.

For some reason the phone completely shuts off AS SOON as it loads the rom (ANY ROM) I even went back to full stock and SAME thing happens. I do mean FULL stock. (Hours of work went into that fun process).

WHAT'S WRONG

- Phone shuts off once it loads into any rom then reboots and repeats the cycle

- Phone DOES NOT shut off if plugged into a power source, stays on without issues and works fine

- I can't use my phone without it being plugged in (battery works fine and charges fine)

WHAT I HAVE TRIED

- I tried cleaning the power button and internals by taking the whole phone apart.

- I checked to see if it was bricked in any way

- I tried different roms and android versions including stock (Yes with factory resets)

I have not tried deleting the entire phone internal memory (formatting it essentially) and re-installing android files back to it.

Any ideas?
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I suggest changing the battery to see if it still behaves that way. I also suggest you to completely start with a clean slate (format everything, including the internal SD, external not necessary) to discard possible issues. Those are the only ideas coming up right now.
[T-Mobile, Samsung Galaxy SIII] Scath:
I'll try and see if its either of those. I also noticed the power button is super sensitive. Light touch sets it off or on. Like capacitative button "light touch " how gentle those are pressed is how gentle I am tapping power and screen responds.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sounds exactly like a faulty power switch, but it could potentially be the battery itself too though.

When you put the battery in, does it try to turn on by itself? If so it's almost certain to be a bad power switch.

Be very careful flashing in this scenario. ESPECIALLY flashing firmware via Odin. If it reboots during the flash it can be very bad news.

This can cause a brick on its own too btw, so i highly recommend getting it fixed ASAP. People have reported having this happen and at some point it just stops powering up at all. Upon further investigation it would show to be hard bricked, sometimes fixable, sometimes not. Basically the constant resetting (like power is permanently pressed) ultimately causes corruption on some of the partitions. It is possible there is already some data corruption present which could cause processes to hang, eat up battery and cause excessive heating.

If you want to be sure it's not the battery itself causing problems though, find someone with another S3 (go to a Tmobile store if you don't know someone) and borrow a battery to test with.

A bad battery can also cause reboots and overheating, but this is much less common than the bad power switch.
[T-Mobile, Samsung Galaxy SIII] Scath:
Sounds like I have three possible causes then... So I will first wipe and format internal memory and re flash everything. Oddly enough it does not reboot when plugged in and sometimes doesn't reboot at all but if I open camera or similar apps it then reboots and won't fully boot just tries to load everything and I get signal and texts come in but then it turns off and reboots again.

Then I'll go to my local spot with an S3 in display lol check battery and see.

Last I'll try and look closer at this power switch, don't think its the cause though. Ill place Collin different positions and see.
[T-Mobile, Samsung Galaxy SIII] Scath:
Even stranger...

So I reformatted my ENTIRE phone internal and external memory. Using multiple devices. Then re formated inside recovery to add the correct folders and files and stuff.

Here is my question.... Previously stated was "Battery could be an issue or Power Switch" -- If these were both the issue why would the phone never turn off in recovery mode? Why would it stay on during boot for long periods of time after flashing?

How can the battery or power switch be the problem when recovery mode keeps the phone on, and I tested this by leaving it on for an hour without it turning off.

The ONLY time it turns off is when the OS is about to boot up Android. If I keep it plugged in, then it boots up fine. What the hell?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
A faulty power switch may not always constantly reboot. I've seen some that do, some that stayed on in Download Mode only, some that only rebooted when held a certain way, some that simply just had an extremely sensitive button, etc. In each case, replacing (or sometimes cleaning/fiddling with it) seemed to fix the issue.

I have also seen problems due to an old or defective battery. As it gets older, it doesn't just lose its ability to hold a charge, but it also gets weaker in that it cannot supply a stable or strong enough level of output. So, for example, it could seem to run ok, but as soon as you try to do something requiring more power, such as using the camera, it can crash because the battery can't provide enough power.

In a case like that, it could easily be able to supply enough to run recovery as its power requirements will be much lower than when you are booted up normal.

You did say it works just fine when plugged in though, and that it only reboots when you try to boot normally. But you also said opening the camera will cause it. This is why I suspect it could be the battery.

You also mentioned that the power button is extremely sensitive though. That is not normal and faulty power buttons happen frequently on this device.

All I'm saying is it could be one, or even both, of those causing your problems. It is possible too though that it's suffering from memory failure, which can result in any number of strange problems.

I am just giving you the most likely possibilities based on past experiences in these forums. I'm not saying it's definitely one or more of these. It could be something else entirely.

Did you ever try the test I asked you about? Remove/reinstall battery. Does it try to turn on by itself when you put it back in?
[T-Mobile, Samsung Galaxy SIII] Scath:
Well Doc, I think everything you just said wrapped it up for me and made a ton of sense.

Sounds like the battery. It overheated prior to this and when I checked the logic board there were no signs of heat stress points I remember when I took the phone casing off when it got hot, the battery was the hottest part that I couldn't touch. I think the battery just gave out finally after all these years of use.

Install and reinstalling the battery the phone does NOT turn on by itself. Not ever. ONLY when it tries to boot the OS does it go into a boot loop where it tries to boot fully then restarts, similarly when you have a very low battery and the phone shuts off right as the OS boots.

Think the battery is the culprit here. :fingers-crossed: I just bought a new glass screen kit for the phone as well, $6 bucks isn't too shabby on ebay. Even though it may suck really bad and be flimsy glass, it's still something! So now the battery will be purchased next -- any suggestions?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I just got a new battery on ebay too, but it's got problems. They sent a free replacement but it's worse than the first. They might be fake "oem" batteries so i dont want to recommend them.

They appear to be from the same lot though, so it could be just bad luck and a bad lot.
[T-Mobile, Samsung Galaxy SIII] serio22:
If you want an OEM battery you're probably better off buying it from Samsung or T-Mobile. I've also heard zerolemon is a good alternative
[Off-topic] tahrang:
Hello

Please post some ideas on what to buy with google play credit.

I am in webdesign, virtual assistant and 3d printing fields.

thanks
[Off-topic] hanisod:
Ehm, you can buy a lot of things, what do you need exactly?
[Off-topic] androidfreak70:
I didn't used them too. Ummm.... I would buy paid apps? I don't even know how to get them :p

TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
[Off-topic] hanisod:
Ehm, you can get them from some stores around here, they're not available in the middle east as far as I know
[Off-topic] androidfreak70:
Ehm ok Ehm. :p :D

TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
[Off-topic] ironman38102:
In Bahrain they are actually available but through a machine that is used for paying bills. You basically feed the money to the machine and it slips out a paper having the redeemable code. Used it once to buy pro version of ROM Manager.
[Off-topic] tfarrelljjr:
How about some music to help you get through your work day? Always good to support artists with the amount of pirating going on nowadays.
[Nexus 9 General] MRobbo80:
There are some really truly great devs in previous version of our beloved nexus devices, And would like to please ask DEVS! To put your HANDS UP if you are going to show your support & efforts in the HTC Nexus 9 :good:

Thank you.

So excited ? ?
[Nexus 9 General] Hashbang173:
I should be able to develop some stuff.
[Nexus 9 General] USBhost:
I will try to make an kernel

for the fun and to learn how
[Nexus 9 General] jd1639:
I'm not a dev, I just know how to do stuff. But I'll be supporting the n9
[Nexus 9 General] MRobbo80:
Top man !

[MENTION=4630246]joshuabg[/MENTION] I appreciated the work you done on the nvidia shield tablet (sent it back) so just a thank you
[Nexus 9 General] i9100g user:
Maybe [MENTION=4684315]flar2[/MENTION] can help you people out :wink:
[Nexus 9 General] DaRkRaGe:
Im ready for preorder too!!!! i need that gorgeous screen sitting on my desk asap ;D~
[Nexus 9 General] MRobbo80:
Don't worry he will be here ;)
[Nexus 9 General] mikereidis:
I'm hoping against hope, that the 2nd HTC Nexus device will be as OTA FM radio capable as the Nexus One was. :)
[Nexus 9 General] MRobbo80:
Looking [MENTION=4684315]flar2[/MENTION] devices look good right

HTC One (m8)*•*HTC One (m7)*•*HTC One XL*•*HTC One S*•*Motorola Xoom*•Nexus 7 (2013)*•*Nexus 5

Perfect match, pretty sure he will be here
[Nexus 9 General] MadMax:
I have not done any dev work in a long time, and not on nexus but I am going to try to learn how to and release something
[Nexus 9 General] USBhost:
Same there
[Nexus 9 General] Hashbang173:
How different do you think Lolipop will be to build for vs Kitkat. I know Lolipop has alot of security.
[Nexus 9 General] MadMax:
Tbh, I have no idea, I use to port sense software, never did much else. I have been wanting to learn so I guess it a better time then never right now
[Nexus 9 General] USBhost:
First off don't build with the security

when i make my own kernel it will not have SELinux on
[Nexus 9 General] Hashbang173:
I usually just port Custom Rom's to devices. Not really port I guess, just have to change the device tree. Do a little bit of kernel stuff to.
[Nexus 9 General] Captain_Throwback:
I don't consider myself a dev, but I will be getting one of these, once the "Sand" version is available.

I am wondering how much more difficult everything is going to be between Lollipop/SELinux and 64-bit capability.

This will be my first Nexus device as well - closest I've had up to now is running GPE on my M8.
[Nexus 9 General] jd1639:
The bootloader will be unlocked so much will be possible. If you've never had a nexus device you're in for a treat!
[Nexus 9 General] skalsson:
Well I thought I'd jump in here and say that this is the device that I'm getting to learn the basis of Java. So I guess I'm like a future dev?
[Nexus 9 General] USBhost:
aren't we all

Im the same as you

time to learn how to hack a kernel
[Nexus 9 General] mrshades812:
Good to see you're getting one also Cap't!

The bootloader will be easily unlocked right out of the box. "fastboot oem unlock" from the bootloader screen and you're done.

It's the root with 5.0 that may prove painful. :)
[Nexus 9 General] USBhost:
Naa

Just disable selinux

And just a few changes to the ram disk and we should be fine
[Nexus 9 General] MRobbo80:
Just have asked flar2, he has order one already!!!!!
[Nexus 9 General] USBhost:
Awesome
[Nexus 9 General] MRobbo80:
I'll ask a few more l8r ;)
[Nexus 9 General] tyvar1:
This is great! I have a feeling that we will get some great ROMs and kernels for this device!
[Nexus 9 General] flar2:
The good thing is Nexus devices are far more open than others, the unknown is the new Tegra SOC, which we don't know how much about. It may take some time to do the stuff that is well established on the more common Qualcomm chips. Stuff like voltage control, overclocking, etc will likely have to be done from scratch. There is a chance that some stuff may not be possible at all, as certain things may be hardcoded into the firmware or hardware or secure encrypted storage directly on the chip (like a sub-kernel), or programmed through e-fuses. Who knows. There is always the possiblity that parts of the hardware are controlled by closed proprietary libraries.

In any case, I don't expect to have a full featured kernel right away after release, as some have come to expect on other devices with the wellknown Qualcomm chips.
[Nexus 9 General] USBhost:
i hope the kernel controls everything

not just a few things

You know maybe you should look at the source code for the nvidia shield tablet

it may shed some light on it
[Nexus 9 General] Hashbang173:
I was thinking of making a hangout for Nexus 9 Development, so we can discuss each others progress in making those custom ROMs (I'm very close BTW). PM your G+ or gmail if interested.
[Nexus 9 General] alicepattinson:
More devs for nexus 9 please. :) Thanks in advance for future nexus 9 devs. :D
[Nexus 9 General] nlua:
This! Just unlocked and rooted!
[Xperia Z Q&A, Help & Troubleshooting] QA Bot:
Q&A for [Tutorial] Xperia Z & ZL Bootloader Unlocking/Relocking

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
[Xperia Z Q&A, Help & Troubleshooting] japansam23:
4.4.4 Bootloader Unlock?

I have an Xperia Z C6616 (10.5.1.A.0.283) that I rooted using easy root via flashtool. However, in the service menu, it says I am unable to unlock the bootloader. Is this true? Will I be forced to flash back to 4.3 to unlock it?
[Xperia Z Q&A, Help & Troubleshooting] kingvortex:
If it says you cannot unlock your bootloader, then you cannot unlock it at all, regardless of which firmware version is installed.

The C6616 bootloader is permanently locked because Bell requested it be that way and there's no way (either officially or unofficially) around it, unfortunately.
[Xperia Z Q&A, Help & Troubleshooting] japansam23:
Well thats incredibly frustrating. Is there any way then to flash new roms or install a recovery? Also, it might not matter, but before I updated to 4.4, it listed my model number as C6606.
[Xperia Z Q&A, Help & Troubleshooting] anticran:
Bootloader Issue

Hey guys, ran into a little issue. I flashed my phone with a stock ROM, C6603_10.3.A.0.423_Generic ES.ftf.

Figuring It'd be fine, I then proceeded to attempt to unlock my bootloader. However, this time after flashing this stock ROM, unlocking the bootloader would cause my phone to crash, resulting in having to reflash the stock rom again.

Any ideas?

Cheers.
[Xperia Z Q&A, Help & Troubleshooting] Kathmandu13:
Please help!

Hello, I need help with unlocking the bootloader for my Sony Xperia Z please. This is the first time I am doing this, so I am a extremely novice on these things. All I want is to flash the sony rom and install android 5 lollipop on my Xperia Z :)

I have done all the steps mentioned above but when I type the command fastboot.exe -I 0x0fce getvar version it just says waiting for device.

I don't know if my phone is even in fastboot mode. I have turned the developer mode on phone setting with USB debugging set to ON. When I connect my phone to the computer I press power and volume up for around 10 second before plugging in the USB. The phone vibrates 3 times and there is a sound in computer but nothing else happens. When I type the command adb devices, it shows no device attached.

I don't know if this is due to me not installing the drivers but I was tried to install Flashtool-drivers-1.5-20140318.exe file, the installation failed. So I went to advance startup setting and disable driver signing. It then installed. I also downloaded the fastboot package and clicked all the exe files. And my phone has its rooting status: Bootloader unlock allowed: Yes

Please help!

:(
[Xperia Z Q&A, Help & Troubleshooting] kingvortex:
You're holding the wrong key combination.

Power your phone OFF first.

When the phone is off, hold volume UP only while connecting your device to your PC. Do not press the power button. The LED should light up blue when done correctly. You can then stop pressing the volume key.

Sent from my C6603
[Xperia Z Q&A, Help & Troubleshooting] Kathmandu13:
Oh Thank you so much! I think I unlocked the bootloader now :)

So what do I need to do now to install custom ROM?

If I understood correctly, I need to flash the current Sony ROM and install different one? Then again what is root? Is unlocking bootloader rooting? Also is the information on the forum up to date? because according to it the newest firmware is 10.3.1.A.0.244/10.3.1.A.2.67. But my firmware is 10.5.1.A.0.292. Please help, I tried finding these information but can't find them.
[Xperia Z Q&A, Help & Troubleshooting] LaurynasVP:
In my own opinion, you shouldn't even unlock your bootloader without getting better known to the entire device and its ROMS/Kernels and etc.,

Anyway, I tink that you haven't made TA pratition backup even, and if I'm right, then you've erased your DRM keys forever without a way getting them back.

But if you have made TA partition backup, then we can proceed to explain next thing.

To flash a custom ROM, you don't have to flash newer nor older software version.

All you have to do is go to your favourite ROM thread and read the instructions very carefully, otherwise you're risking to brick/soft-brick your device.

But on different ROMs can be different flashing guides, for example, we can take "Validus" ROM:

VALIDUS

Flashing instructions are : (I'm going to quote them)

So in overall, that mean at first you've to have CWM (ClockWorkMod Recovery) (but I think that it's not necessary if you would flash boot.img with it either way)

Secondly, you've to put the entire ROM in your SD Card (not in phone memory), you can include gapps as well,

Third, you need to extract the file named "boot.img" from the ROM which you've downloaded (Now i'm talking about VALIDUS and ONLY IF YOU'RE GOING TO INSTALL THIS ROM EXACTLY), but don't remove it from .rar/.zip.

After you've done everything what is written above, you can flash boot.img using the command prompt and fastboot file, which you were using to unlock your bootloader.

The command is this : fastboot flash boot boot.img

Then, write fastboot reboot and as soon as your LED will change color, push the volume up rocker and then you will be in recovery. After that, go to "Apply Update" --> "Choose from files" or sth (don't remember now), --> "Validus.zip/.rar". and optional you can flash gapps either.

And then pus the button to "Reboot now".

That's all - you've newest Validus build.

But the main point is that for example you would take Pabx rom, you'll have to do everything using CMD (fastboot)

PABX's ROM YUGA L

Look at yourself and compare everything.

Validus ROM is customized than Pabx ROM. It has more customatizations either : APPS, Control, Mods, Gesture and etc., and Pabx ROM is pure-stock L (I think).

I hope I anwered to all ur questions, if not - quote me
[Xperia Z Q&A, Help & Troubleshooting] Kathmandu13:
Thanks!

Thank you very much for your reply and yes perhaps you are right. I should not mess with my phone's software. My skill and knowledge on this is extremely limited. I think I did unlock my bootloader but I will leave it on that. My phone still runs fine for now. Unless I find some tutorial videos which I can understand, I will stay away from flashing my phone :D

Thanks again for help.