Bugs, bugs, bugs on stock KitKat. - G 2014 Q&A, Help & Troubleshooting

Hello,
I'm considering sending in my moto g for replacement, but after lots of research, I still can't find any consistent information on whether these bugs are common, fixed by updating to lollipop, or indicate that my phone is broken.
1. Data drops randomly and I have to go in and out of airplane mode several times to get it back.
2. One Sim loses signal until doing the above mentioned.
3. Phone can't make or receive calls on one or both Sims, even though it's supposedly connected. Fixable only by rebooting phone.
4. Earpiece buzzing annoyingly when in-call, whether data's on or off.
What do you guys think, do you experience the same, if so did lollipop fix it for you?
I suppose, that Motorola would just tell me to do a factory reset. Is it even possible to send in a phone for repair, for being buggy?
Thanks for any suggestions.

Related

Many many problems with KitKat update, what are my options?

I am stock, unrooted, and I installed the KitKat update a couple of weeks ago and my phone is absolutely terrible now.
1. Getting the "no-sim" (no sprint sim, no 4G for you!) error message, which I have never gotten before on this phone. I get the error intermittantly after installing the kitkat update
2. Battery drain is substantial, about twice the rate of what it was before
3. Phone runs much warmer than normal
4. Very bad reception, texts and calls not going through. I used to be able to get full bars 4G in my house, now I don't even get 3G after the update, and I had a 30 minute phone conversation from my house the other day and I dropped the call 4 times.
I thought maybe it was just a tower issue but it's been like this for the past few weeks. I've tried doing a PRL update, profile update, etc. but nothing helps.
Is the reception issue a problem with the most recent PRL update?
If I root the phone and install a custom ROM will this address my problems? I've rooted my tablets before but not a phone. Would going over to CM solve these issues?
I had the same problem way back on this phone and it was the SIM had gone bad. I would definitely expect that yours has just gone bad. That would cause your battery to drain due to constantly seeking network but SIM won't register. Which would also likely cause the excessive heat too.
I hope this is all the problem is for you. It was a simple fix at the Sprint store. Good luck!!!
Sent from my HTC One using Tapatalk
take the sim card out and clean it maybe? and do a factory reset after you backup?(of course, unless you root and use some software to backup, all other backup methods just won't help too much)
Reason been, I had the total stock phone when I did the KK update on Feb 1st I think, and I didn't see any problem other than somehow enabled my google voice. No signal problem(same s..t as the dec update last year, before that it was even worse) and no battery problem(turned on the stock battery saving)
I had problems (2) and (3), and a few others, since installing the update. In my case, the GPS receiving notification would flash incessantly, and Location Services seemed to be the battery drain culprit, I could dramatically reduce the drain by turning the GPS off (not a great solution).
The answer, at least in my case, was a hard reset. I did that, reinstalled my apps, and the GPS / battery issue has gone away. I was also having other intermittent weird issues that have gone away since reinstalling. I guess the upgrade must have corrupted some things...
Sent from my iPad using Tapatalk
Hard reset your phone and clean the SIM card. You should be all good then. Kit Kat should have the opposite effect on your battery life. I usually get 10+ hours on a charge. Matters what I'm doing with my phone.
Sent from my HTCONE using Tapatalk
Just wanted to add that my phone has suffered from none of the issues above. I'm using it on a GSM network in India and running InsertCoin Rom. Everything works well. Battery has been decent and I can easily pull 12 hrs plus
Sent from my HTCONE using Tapatalk
So I did the factory reset this weekend. Just to confirm, the factory reset reverts me back to KitKat, not Jelly Bean, which was what the phone originally came with. Just want to confirm I did the reset correctly.
I dont think you can downgrade from KitKat to Jellybean not on stock atleast.
SeriesOfTubes said:
So I did the factory reset this weekend. Just to confirm, the factory reset reverts me back to KitKat, not Jelly Bean, which was what the phone originally came with. Just want to confirm I did the reset correctly.
Click to expand...
Click to collapse
when you took the OverTheAir upgrade package, it will get into bootloader and change(upgrade) your phone's ROM(not really Read Only Memory any more, but still carry that name) and from then on, you will have to use the bootloader to reload the old jelly bean to get back to JB, otherwise, no matter how you reset, it'll be KK. (the reload process requires special files and procedures, with computer and USB cables) Although "factory reset" won't revert back to the "original factory settings" that came with the phone at the time you bought it, it will wipe out all the settings and apps and anything that's not set by the factory default. After the so called factory reset, your phone will get into a state that the "factory" testers have, which should be a stable state because the "factory" supposed to do a lot of tests based on that state and pass all those tests. This will give you a nice baseline about which could be wrong, the hardware, the network, or the software. Though, it won't be always true because human make mistakes, so the "factory" could release a software that's buggy. like the one we got on last dec, but still, once you get to the so called "factory" state, which all the other phones using the same hardware and software will get to the same point, you can be sure that no other unknown factors are causing your problems. It's like you have the exact same thing on your hand as somebody else on the other side of the planet, so other people can do the tests required to figure out your problems. Will that help you for some apps you want to run that crash your phone or cause big problem? No, that's the responsibility of the apps' developers, not the phone manufacturer. in that case, you'll have to give up that app.

[Q] Input Issues and Data Connection Drops

Hey there.
I have a stock Samsung Galaxy S4 Active on the AT&T network. Recently, I've been plagued by a number of troubles.
Bit of background:
For a while, I had the most bizarre issue: the screen thought I was touching it when I wasn't, near the bottom-middle of the screen, and would attempt to open/click on anything in that area. Often turning the screen on and off would help, for a little while. I was reaching my wits' end, because that would obviously be very frustrating to someone who uses their phone frequently throughout the day.
I thought maybe it had been new software I had installed, so I did a factory reset. Problem remained. I factory reset with NO backups. Problem remained. I updated to 4.4.2 via OTA. Problem remained...
And then mysteriously went away on its own.
I've been working in tech for a decade now, mainly in PC and server architecture, so I know better than to look a gift horse in the mouth - but I also know better than to think a problem that "mysteriously" goes away is gone for good. So the first part of my question: does anyone know what could have possibly been causing this?
I'm not super phone-savvy. I've rooted and flashed a few phones in the past couple years, but I'm by no means developer-level.
---------------------
Which brings me to my next problem... around the time that this issue went away, another one cropped up. Randomly, my phone will stop sending/receiving texts/calls, and the data connection will not function. This will continue until I turn on airplane mode and turn it off--at that point I receive all my missed texts, and it works again... sometimes for 5 minutes, sometimes for nearly 2 days. It's really frustrating. I've tried factory resets, I've tried restoring default APNs... but I'm at my wit's end with this. Can anyone help?
Thanks!
I should add that, with my last issue, it still shows a data connection in the notification bar - but there is none, or at least, no activity on it. It doesn't simply act as if it's in airplane mode and go "wah no data network" as soon as I try using it--it just simply hangs for ~30 seconds, then times out. Messages don't get received, webpages don't load, calls don't get placed, etc.

Moto G 2014 hangs during incoming calls resulting in call drops

Hello!
My first thread on this one of a kind forum! So here's my problem: sometimes, when I get a call, the phone lights up and shows the caller name and call receiving interface, but no matter how many times I swipe left or right, it hangs and eventually the call drops. But on the other side, the call keeps on ringing. Which means the person on the other side thinks I am a lazy bum who never picks up :| (ie. My mother :|) There are good days and the bad days, meaning, I experience only one or two call drops on some days and then there are days when every freaking call gets dropped.
Solutions I have tried:
1) I noticed the problem first when I updated my phone to lollipop (official update). So I figured maybe the update was at fault. When the problem got severe I decided to roll the version back to kitkat. So I unlocked the boot loader and flashed the firmware.
2) Unfortunately, the problem persisted even then. It's important to understand this problem only started after the update. First four months with original firmware were total bliss.
3) Since even the original firmware gave me a lot of hell I decided to bid adieu to the whole institution of moto firmware and flashed cyanogen 12. The problem is still sometimes evident. Not as much as the moto firmware. But it's still there.
What to do? Is my hardware at fault? I hope not. If not the hardware, then how to fix this software problem? And why is it happening in cyanogen if it's a moto firmware issue? What can I do? Please help! Thanks.

Some issues I've had (2 days in)

Love the device, but this one is going in for an exchange. Not sure if it will resolve the issues I had, but my phone was behaving badly. I unlocked and rooted it about 10 minutes after I got it, using the Chainfire method here..
1) WiFi reception is awesome, except it drops the connection constantly! I have an entry level commercial AP (Unifi) and the thing is awesome. All kinds of devices connected to it, but this Moto can't stay connected. From the logs on the controller, it appears to be switching channels constantly. Wifi goes from all bars to bars with x to off.
2) Reboot results in bootloop. On more than one occasion, I had to reset the device multiple times to get it to boot. This morning, I could not get it to complete a boot at all. I've since reflashed the Tmo stock ROM.
3) Lookout randomly comes back! Froze it with TiBu, stop and disable in app manager... nothing kills it! Reason 1 for root!
The WiFi issue is a killer. Again, I am going to take this one in and exchange it for another and hopefully the WiFi issue is gone. I think I'll need to restrain myself from rooting until I pass the exchange date.
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
forty9er said:
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
Click to expand...
Click to collapse
Thanks! I will give that a shot before I take it in.
I've been back on stock with unlocked bootloader for a day and change, and I still get WiFi drops. It seems to happen more with BT on, but they certainly haven't gone away. I've changed a bunch of things on my AP to try and eliminate them too, but it hasn't helped much. I may try disabling the A/C radio (which fixes it for some), but that's hardly an answer. I am starting to think that this is a Nougat or a Qualcomm issue.
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Sent from my Moto Z (2) using Tapatalk
Tidbits said:
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Click to expand...
Click to collapse
Well, it seems I'm not the only one.
https://forums.lenovo.com/t5/Moto-Z...terprise-type-5Ghz-band-802-11AC/td-p/3816198
I actually have this issue with another device too , so I think it's either an Android, AP or a Qualcomm thing. Some have said turning off the A/C/N radio helps, but that's not a "solution."

Speaker phone automatically turning on while receiving call

Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
shashankkp12 said:
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
Click to expand...
Click to collapse
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
TeddyBeers said:
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
Click to expand...
Click to collapse
Thanks for the suggestion, But by full factory reset do you mean the hard reset from the recovery menu or just the factory reset from settings menu -> factory reset..?
facing same issue please help
i am facign the same issue please help me out
Still no solution for the problem...I have made an habit to turn speaker phone on and off immediately after calling .
Try Macrodroid app to set an automatic task, to turn speaker off 1 or to seconds after receiving call.
I am also facing Same issue, can any one give suggestions
Somehow that happened to me when I just got the phone a few months ago. I think that was still on 8.0.
But tapping the speaker phone button 2 times everytime I have a call became nature for me and eventually after a few days, I no longer have that issue.
Are you still having that speaker phone issue now?
Yes...but while it was consistent on 8.0 it has become a random occurrence after 8.1 update
same issue
factory reset solution is not acceptable.

Categories

Resources