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.
Related
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One
Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.
I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue
Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman
The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE
Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman
My first day with the Droid bionic... it's my first non-Samsung Android phone, so I'm not sure what to think.
In the midst of trying to figure it out and get it all setup (rooted, Titanium Backup restore, apps only), and my data drops out. Apparently for good.
I had solid 4G data when I first opened up the phone this afternoon. I ran some speed tests and switched to WiFi. I left the house a bit later and realized I couldn't open a webpage. I noticed the WiFi was still on, so I shut it off, but the cellular data never came back.
Tried putting it in airplane mode and back, rebooted (several times), tried the data toggle on the power control widget, I even forced the phone into CDMA only mode (and back).
I'm stumped. Has anyone else seen this? Is there any kind of possibility that restoring apps or rooting could have anything to do with it? I have not seen this problem over many a ROM on the Vibrant, and then the Droid Charge. I even loaded a GB ROM on the Charge and restored all my apps without issue.
Any help would be appreciated. I'd really not like to have to wipe the phone and start over.
I had something similar happen although I'm not rooted yet. For 3 days I was golden. Then I installed switchpro widget to see how the 3G/4G toggle worked with the Bionic and it made my mobile connectivity wonky. I uninstalled it. It still is wonky today.
LTE is there then goes away a reboot corrects it until it goes away. 3G is exactly the same. Turn on WIFI and the LTE disappears. It's supposed to stay up just turn white like it did for 3 days prior to installing then uninstalling switchpro. It could just be coincidence with the switchpro thing idk. I'm not all that knowledgeable with APN's, but after some research somehow I believe mine got mixed up via switchpro. Getting a new Bionic tomorrow.
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Flapjack said:
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
I'd get another one then. Or if you don't want to do that get a different brand
I think I'll just try a hard reset. I'm sure it was something I did with Titanium backup... I'll just have to figure out what.
Or you could try a factory reset to see if that solves it
EDIT: I see you thought of that 1st
Something similar happened to me. The only way I could fix it was by restarting the phone until the data crashed again. I solved this problem (or I think I did, still testing it) by removing all my widgets. I have a strong suspicion it was a widget doing this (specifically the AIX weather widget, but I am not sure yet).
So, I suggest that you remove all of your widgets and restart your phone and see what happens.
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
I'm thinking its got to be something related to wifi. every time I disconnect from wifi I can't connect to data unless I reset my phone.
Sent from my DROID BIONIC using XDA App
Flapjack said:
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
Click to expand...
Click to collapse
Glad to hear that. Factory reset did not fix it for me. Will have a new tomorrow
I am also having this problem. If Motorola still used vanilla android this wouldn't be an issue. I hate when manufacturers feel it necessary to fix something that isn't broke. I am sad to see how many people are experiencing this problem because if it was isolated to my phone and a few others then a warranty replacement would do the trick. I now feel like I wasted 380 on phone and accessories. I placed a call to Verizon tech support and their as clueless as usual. I hope an update is released soon that fixes this issue (or a custom rom). I remain hopeful that we start seeing good things on our Motorola devices now that google owns moto.
NOTE: I wish people would start reading through existing threads before starting new ones. I started a thread to this effect back on day 3. Several others have started threads to this effect as well. I think there are now 4 or 5 on this very same subject.
Sent from my DROID BIONIC using xda premium
I posted this in an older thread but figured I would just go ahead and make a separate post about it.
Ever since I updated the phone to 5.1 it has crashed repeatedly, super laggy, battery life is significantly worse than kitkat, Turbo charge seems to take longer than on kitkat, my texts and calls won't go through, and on a rare occasion my phone will reboot by itself. I've cleared the cache regularly and have factory reset a couple of times and the problems will go away for about a week, but only to return again. I'm going to Verizon tomorrow to see if they can do anything.
Anybody else have these issues with their Turbo?
Sent from my XT1254 using XDA Forums
I'm not experiencing any of this. Have you troubleshot apps that you have downloaded as possible culprits? Also, did you upgrade via OTA or did you manually flash the 5.1 update via rootjunky? I've heard multiple people having issues with the flashed one.
Maybe it's one of the apps you have installed. Try a FDR and install your apps a few at a times. Try to pinpoint which app is constantly taxing your phone. If all else fails make verizon give you another 4.4.4 Turbo
So I went to Verizon yesterday and they couldn't do anything for me. I just took the OTA that came out yesterday and I am hoping it fixes more than the stage fright exploit. If not I guess I will be migrating back down to my old Galaxy S4.
Murd0c said:
So I went to Verizon yesterday and they couldn't do anything for me. I just took the OTA that came out yesterday and I am hoping it fixes more than the stage fright exploit. If not I guess I will be migrating back down to my old Galaxy S4.
Click to expand...
Click to collapse
If you haven't already, try using the Verizon Upgrade Assistant (that annoying thing that pops up every time you plug your phone into a computer) and select repair. This will do the cleanest wipe possible, reflash everything and bring you up the the latest firmware version. If you still have problems after that, chances are you're using an app that lollipop doesn't like, or you have a physically defective unit.
I ended up with what I think was a physically defective unit, and I got a warranty replacement straight from Motorola. The process was painless, and as long as the phone doesn't have any physical damage and was never exposed to water (in most modern phones, there's a water-sensitive sticker on the inside that changes color when exposed to water, so they can tell if you're lying), you basically just have to ask for it.
In fact, forget what I said in my first paragraph. Just get the Motorola replacement.
https://motorola-global-portal.cust...sion/L3RpbWUvMTQ0NDMzNDc3Mi9zaWQvWDgyS2RzeW0=
OK guys quick update I sucked it up and got the Motorola replacement and it works perfectly now, turns out I had a factory fault or something
My phone isn't laggy, but my Turbo charging is definitely slower, my WiFi is hit or miss at times, and the battery does seem to drain a bit faster but isn't too awful.
Sent from my Droid Turbo using XDA
ATT auto updated my phone. Everything seems to work like it should except that the area next to my sim card is hot enough to burn me. If I put my phone in airplane mode everything is fine. My battery life is less than 4hrs. I have done a factory reset with no success. I want to install a custom rom but I cannot find a root for this new version. Is there any way to install a new rom with no root?
luxveritas said:
ATT auto updated my phone. Everything seems to work like it should except that the area next to my sim card is hot enough to burn me. If I put my phone in airplane mode everything is fine. My battery life is less than 4hrs. I have done a factory reset with no success. I want to install a custom rom but I cannot find a root for this new version. Is there any way to install a new rom with no root?
Click to expand...
Click to collapse
I am also having the same issues. I thought it was a hardware problem, but after seeing your post I'm suspecting it is something else. I even went to the AT&T store to get a new SIM just in case that was the issue. It suxs, my phone is getting intermittent network connectivity and the right side of the phone is roasting. I also performed a factory reset to no avail... Anyone else having this issue?
I am having the exact same issue. Its basically made my phone unusable. Once the phone starts connecting/talking it gets very hot and i lose cell service. It like the cell radio starts working overtime, over heats and stops working . I have to put it in airplane mode t get the phone to cool down. Not sure what to do since it seems like a software issue. All started after the update.
krperegrin said:
I am having the exact same issue. Its basically made my phone unusable. Once the phone starts connecting/talking it gets very hot and i lose cell service. It like the cell radio starts working overtime, over heats and stops working . I have to put it in airplane mode t get the phone to cool down. Not sure what to do since it seems like a software issue. All started after the update.
Click to expand...
Click to collapse
Since my phone is unusable and there is nothing I can do software wise (Installed all AT&T updates and performed factory reset), I decided to call Samsung and put the phone in for a warranty repair. We shall see what happens after the 9 days it takes them to make repairs. Guessing that they wont actually troubleshoot the issue, just verify nothing is physically wrong with the phone, liquid spill, drop damage, etc. and then just send me a clean referb.
Success!!!
I performed a factory reset and set the phone up as a new phone ignoring my backups. I installed all the updates and everything is working again.
The locked bootloader on this phone is bull****. ATT/Samsung broke my phone with an update and I could not install root to fix it myself. I will only buy apple or google phones from now on. I hope that the companies that make the OS might be a little more careful with their updates.
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."