Alright guys, so here's a strange issue that I encountered on day 1 of owning my Pixel XL (NDE63N, 32GB/Verizon):
Unlocked bootloader, rooted, installed all available play store updates, configured the phone how I wanted it, and everything was great.
I played with the phone on and off throughout the day with zero issues.
I installed a few of my favorite apps: URET, cSploit, zAnti,etc..
Ok, on with what happened: I was holding the phone, reading a forum post, when all of a sudden an error pops up "System UI has stopped."
This error repeatedly pops up no matter how many times you cancel it, and no other buttons work (minus the power button.)
- Alright, so I rebooted(several times,) no luck.
- Rebooted into safe mode - no luck.
- Tried to get into recovery to factory reset - no luck (just showed Android with exclamation point.)
- Finally decided against my will that I was going to just re load the factory image through fastboot..
Well, the device was powered on, and I plugged it into USB to see if ADB would recognize it. But for some reason the phone returned to normal! I unplugged it, and it went back to the error.. Plugged it back in, it was back to normal again.
I uninstalled URET, and all is well again!
Not quite sure how/why a USB connection would *fix* the error message temporarily, but it did!
So, in case any of you have the same issue, just try to plug it into your computer before you try to reset your phone lol
Sorry for the long post for such an easy fix, but I figured I'd be as detailed as possible in case someone else has a similar situation.
Sent from my Pixel XL using Tapatalk
battery level below 15% when this is happening? That was a side effect of the Sr1 for supersu
UrGonnaDie1 said:
battery level below 15% when this is happening? That was a side effect of the Sr1 for supersu
Click to expand...
Click to collapse
Hmm, that's weird! I honestly have no idea if it was or not!
I feel like maybe I didn't just figure out a stupid trick to help people out, haha
Thank you for letting me know that.
Edit: I just checked, and I'm on SR2, so I wonder if the issue persisted across it. Going to update to SR3 or 4 now.
Sent from my Pixel XL using Tapatalk
foil said:
Hmm, that's weird! I honestly have no idea if it was or not!
I feel like maybe I didn't just figure out a stupid trick to help people out, haha
Thank you for letting me know that.
Edit: I just checked, and I'm on SR2, so I wonder if the issue persisted across it. Going to update to SR3 or 4 now.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
So did any of those solve the issue?
Related
Okay so ive been running jmt v8 for about a week on my phone and everything was running great. Then yesterday morning my phone became very slow and unusable. Then i started getting the error message acore system has stopped working and the phone would randomly restart and then it would start vibrating then stop then vibrate again and so on. So i insalled a new rom and i stopped getting the core system has stopped error but i am still getting the random reboots. And the screen also wakes up by itself. Please any help or suggestions would be greatly appreciated.
Sent from my cm_tenderloin using Tapatalk 2
I just had this fixed. There's something wrong with the power sensor, especially if it tries to boot the second you put the battery in without touching the power button.
Unfortunately you've been rooted now and because of the issues, you can't flash stock and reset the root count. So you can't sent to your carrier.
Fortunately, http://www.mobiletechvideos.com fixes EXACTLY this for $35 minus shipping it to them. I got my phone back today and it's just the way it was ROM wise and all my files are there and the issue is fixed.
This is a pretty common T989 issue.
Justananomaly said:
I just had this fixed. There's something wrong with the power sensor, especially if it tries to boot the second you put the battery in without touching the power button.
Unfortunately you've been rooted now and because of the issues, you can't flash stock and reset the root count. So you can't sent to your carrier.
Fortunately, http://www.mobiletechvideos.com fixes EXACTLY this for $35 minus shipping it to them. I got my phone back today and it's just the way it was ROM wise and all my files are there and the issue is fixed.
This is a pretty common T989 issue.
Click to expand...
Click to collapse
That's exactly my problem but are you sure this company is reliable?
Sent from my cm_tenderloin using Tapatalk 2
And can you also give me the link to the exact thing you ordered because i couldn't find it on their site, thanks !
Sent from my cm_tenderloin using Tapatalk 2
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile-power-button-repair/
And yes, I was sceptical too. Josh, the owner, is reachable by email and answers pretty quickly and did an amazing job repairing my phone.
You Can Boot into Recovery? Darkside Wipes, Flash another Rom, Dalvik Cache wipe,Format System,Fix Permissions.
Dennisalex said:
You Can Boot into Recovery? Darkside Wipes, Flash another Rom, Dalvik Cache wipe,Format System,Fix Permissions.
Click to expand...
Click to collapse
I can boot into recovery but its tricky because I have to press the buttons perfect or it'll just reboot. I believe the problem is with the power button and ill probably get it replaced.
Sent from my cm_tenderloin using Tapatalk 2
I have same problem last month, send the rooted phone to Samsung. After 15 days .I get back my phone for free.
I hope this can help you.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
For anyone with key issues and need to get into recovery or download mode there are adb commands that do this. We get too comfortable with apps and forget about the manual way of achieving a lot of the same tasks that apps provide for us.
From a command prompt:
adb reboot recovery
adb reboot download
playya said:
For anyone with key issues and need to get into recovery or download mode there are adb commands that do this. We get too comfortable with apps and forget about the manual way of achieving a lot of the same tasks that apps provide for us.
From a command prompt:
adb reboot recovery
adb reboot download
Click to expand...
Click to collapse
Thanks I will be trying this out.
Sent from my cm_tenderloin using Tapatalk 2
hey guys. after the ics update my phone started to lock up and its not rooted. now all of a sudden when i put the battery in it it vibrates once then starts to load and gets about half way and stops. then it turns off and just vibrates a few seconds and vibrates but the screen never shows anything. tryed using just a usb with the battery out and it skips the load screen and automatically starts vibrate looping. the power button seems stuck but i dont think i can fix it any ideas?
Hey everyone! I have a similar (but not quite the same) problem. Every now and then my phone "tells" me to restart it for maximum performance. Every time I restart or just turn on my phone it goes through the boot cycle, including a message that says "android is upgrading" (I got the ICS upgrade from Kies prior to rooting my phone). Then, all of a sudden, the phone doesn't work, and it starts the boot cycle all over again. This happens several times in a row, which for me is a safety issue because I'm not able to call Big Jon (my husband) to get me from the train late at night. Any fixes for that? Thanks.
sparkie6point0 said:
Hey everyone! I have a similar (but not quite the same) problem. Every now and then my phone "tells" me to restart it for maximum performance. Every time I restart or just turn on my phone it goes through the boot cycle, including a message that says "android is upgrading" (I got the ICS upgrade from Kies prior to rooting my phone). Then, all of a sudden, the phone doesn't work, and it starts the boot cycle all over again. This happens several times in a row, which for me is a safety issue because I'm not able to call Big Jon (my husband) to get me from the train late at night. Any fixes for that? Thanks.
Click to expand...
Click to collapse
You may have to run fix permissions in recovery are you rooted
Sent from my SGH-T989 using Tapatalk 2
Warranty exchange it. Known problem
Sent from my SGH-T989 using xda app-developers app
Same problem
And the vest part is that i can't replace it cause i live in India
Sent from my SGH-T989 using xda app-developers app
Damn! Just found this thread...sounds like what my phone started doing today!!
I was clicking around on gmail, then back to home screen, the camera FLASHED all by itself without me doing anything, then started the boot loop thing. Clicking the power button only made it worse. Finally was able to get into recovery via TWRP...but that was weird too. I did a factory reset/wipe and was going to reinstall The Sith ROM that I was running, but it just rebooted and loaded up The Sith anyway and it should have been cleared. I then tried to restore back to Beastmade ROM, restore was very quick and said successful but it booted back to Sith.
Now the power button is hyper sensitive! All I have to do is brush the power button and it will light up the screen. Touch it too long and it will bring up the boot menu. I'm afraid to actually CLICK the button as it might go haywire again.
WTF is going on!? This all seems really odd that it's going down with some of these new ROMs being released. I wasn't even touching the power button when all this started. The weird clicks and flashes didn't sound good when it was all going on.
Has anyone tried flashing back to and OLD rom to see if it will fix it?
change settings to interactive/deadline
Hi, new here but I've been lurking for a while.
I followed Powerpoint's guide to instal CM10 on my KF2
http://forum.xda-developers.com/showthread.php?t=2105077
Everything was running great and has been since I first loaded version 3 a few weeks ago, and last week i went to version 4 of powerpoint's rom with no problems. Then a couple days ago after i had been browsing the internet on it for maybe 30 minutes, I set it down and when i came back the screen was off and wouldn't turn back on. so i figured the battery was just dead, so i plugged it in to the wall charger. At first the charge/power light wouldn't come on at all. Then after several plugs and unplugs the orange light started to come on but would only stay illuminated for 30 seconds-ish. So I tried it on my phone charger and the orange light came on and stayed on, so i decided to let it charge overnight. The next morning the light was still glowing orange so I unplugged it and tried turning it on, but still nothing happens. But when I plugged it back in afterwards the light came on green. now it has been plugged in for almost a day with the green light on but it still wont turn on.
Anyone else have this problem? Any ideas what i can try? for obvious reasons i can't exactly ship it back to amazon lol
p.s. I have a final on friday and the text book for that class is on the kindle. So urgent responses will be greatly appreciated.
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
docnougat said:
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I've had this a couple of times on both 10.1 ROMs. As you stated the only way I got it working was to hold the power button for 20 secs, then power on normally.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
docnougat said:
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
Click to expand...
Click to collapse
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
agreed, if it was happening while i was trying to do stuff it would be problem. As it is though, I just consider it a minor inconvenience. Glad to know I'm not the only one experiencing this though.
iytrix said:
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
Click to expand...
Click to collapse
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
fmkilo said:
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
Click to expand...
Click to collapse
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
or you could have kmsg being written to a file during it...
the hard reset (power button for 20s) clears memory
So i have had my zenfone for awhile now. i unlocked the bootloader and was able to root it with a temp CWM. it was going fine for a long time.
Then one day my phone started to act up. wouldn't read texts right, false notifications, and app crashing. i thought maybe i had a virus so i ran a cleaning app (Clean Master and Lookout) but they found nothing. so i thought why not restarting the phone? seems to work for some.... *sigh*
Upon restarting the phone i am now stuck on the ZenPhone flip case thing... with the info on the circle. i thought maybe i dropped my phone sometime or somewhere and the case got stuck. okay simple fix, i tried using a magnet to open the case... and it did nothing.
Then I tired going into recovery mode by going through fast boot. but selecting anything in fast boot causes the phone to "freeze" and endlessly vibrate. It can't even detect when its plugged into the computer so i cant do commands on it from fast boot. i cant even do it from the OS as i think when its in the flip thing it doesn't allow PC access (at least i think). but the strange part about being on the OS, is that when phone goes to sleep (screen turns off), it "freezes".
What i'm asking here is there a way to fix this or is this phone lost. i made this account just for this... please help!
Good luck, I wish I had never bought this phone. I've sent it back to A-Sucks two damn times and it's still nothing more than a phone that always has some kind of an issue.
Chocketbear said:
Good luck, I wish I had never bought this phone. I've sent it back to A-Sucks two damn times and it's still nothing more than a phone that always has some kind of an issue.
Click to expand...
Click to collapse
Well i'm not one for giving up so easily. tho i am stumped on this, i would like it if i didnt have to send this back to asus... plus i think i voided my warranty.
Sonrio224 said:
Well i'm not one for giving up so easily. tho i am stumped on this, i would like it if i didnt have to send this back to asus... plus i think i voided my warranty.
Click to expand...
Click to collapse
You have a different issue, yeah don't send it back.
Maybe you can try twrp manager app to flash recovery if you can boot the system
titou4488 said:
Maybe you can try twrp manager app to flash recovery if you can boot the system
Click to expand...
Click to collapse
I tried that. my computer, or any other computer i tried, doesn't detect its connected when in fast boot nor in the OS.
when trying to use the normal recovery on the phone. it gets stuck in an endless vibration until i turn it off.
Booting into anything (i.e. Normal boot, recovery) from fast boot causes the vibration hang
Sonrio224 said:
I tried that. my computer, or any other computer i tried, doesn't detect its connected when in fast boot nor in the OS.
when trying to use the normal recovery on the phone. it gets stuck in an endless vibration until i turn it off.
Booting into anything (i.e. Normal boot, recovery) from fast boot causes the vibration hang
Click to expand...
Click to collapse
Re-read that, nothing was said about the PC...
ultramag69 said:
Re-read that, nothing was said about the PC...
Click to expand...
Click to collapse
my bad... either way, i still cant get into the OS as its stuck on the ZenPhone flip case thing as i stated above. it wont let me do anything from there.
if the phone cannot be saved. i might as well sell it for parts.
Before that, have you tried totally discharging the battery, leaving for a day or 2 to get rid of any last traces of power from the RAM then recharging and starting up again?
Might be something screwy going on with the phones hardware but these things are literally PC's and sometimes they need to have a good shutdown to get rid of all the quirks stuck in ram.
If you don't want to wait, you could just open up and disconnect the battery. You were only going to sell as parts anyway....
ultramag69 said:
Before that, have you tried totally discharging the battery, leaving for a day or 2 to get rid of any last traces of power from the RAM then recharging and starting up again?
Might be something screwy going on with the phones hardware but these things are literally PC's and sometimes they need to have a good shutdown to get rid of all the quirks stuck in ram.
If you don't want to wait, you could just open up and disconnect the battery. You were only going to sell as parts anyway....
Click to expand...
Click to collapse
haven't tried that. ill fully drain the battery and see where i get
Okay so good news. that actually worked... i think. i took the battery out for a bit and let it sit, then i put it back in and it booted up just fine!
but now i have a new issue, i can no longer talk on phone calls. speaker isn't working for some reason. might have put it back together wrong.
all things considered, thank you so much for the help!
No worries, good luck on the speaker issue...
I just got my brand new OP3, opened it and turned it on to start setting it up, it freezes inside the android set up and then restarts itself after a few seconds of being frozen.
Any solutions? I really don't want to return it, I find it a bit stupid it doesn't even work out of the box
Might be a dud. They happen. RMA it.
LaysDarren said:
I just got my brand new OP3, opened it and turned it on to start setting it up, it freezes inside the android set up and then restarts itself after a few seconds of being frozen.
Any solutions? I really don't want to return it, I find it a bit stupid it doesn't even work out of the box
Click to expand...
Click to collapse
I don't own this phone, but this happened to me with a Nexus, I turned it off, was able to get into recovery mode with button combinations, then I factory reset, cleared cache, and rebooted, it was fine.
I hope you can give it a try
Sent from my XT1097 using XDA-Developers mobile app
mr mystery said:
Might be a dud. They happen. RMA it.
Click to expand...
Click to collapse
markdexter said:
I don't own this phone, but this happened to me with a Nexus, I turned it off, was able to get into recovery mode with button combinations, then I factory reset, cleared cache, and rebooted, it was fine.
I hope you can give it a try
Click to expand...
Click to collapse
Tried doing the Factory reset thing, no luck. Talked to OP support and the guy told me to submit a ticket with my issues, and that a "level 2 technician" would help me.
So I got home and plugged it into my PC, turns out the phone doesn't freeze when plugged in via USB. But on the included charger, and without being plugged into anything, it freezes and reboots itself in a continuous loop.
Keep us informed I'd like to hear what the problem/solution is
Hello, i have the same issue, did u find the solution ?
tenzeu said:
Hello, i have the same issue, did u find the solution ?
Click to expand...
Click to collapse
I also had my Oneplus 3 in a bootloop and freezing while showing either the 1+ square or the rotating red dots.
After I tried to get it repaired by talking with support and had been using my old phone for a few days and reflashing the ROM and recovery many times. I got it working again (ish) now it only freezes ones a day.
Support is a pain, I'm waiting for a level 2 techician for almost a week now.
So I any of you know a solution or have a confirmation that it is a hardware failure, I think we all would like to hear about it.
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.