Runtime Error bad argument#1 to 'abs' (number expected, got nil) - Galaxy Note 4 Q&A, Help & Troubleshooting

hello,
my note 4 has been working pretty good up until maybe a week ago, and then it started to randomly turn off and sometimes it would re-boot. other times pushing the home button it wouldnt awake, even thou the blue led lights was flashing like i had a message or notification, pushing any button would not awaken it, pushing and holding the power button would not turn it off, prompting me to pull the battery out. put the battery back in, push and hold the power button had no effect, having to volume down, home button, and push power button, and then volume down when prompted would boot the phone.
many times the phone would freeze, and pop up window would say X app has stopped working do you want to shut it down?, play store, samsung ui, various apps.
so, i googled my symptons, several suggestions suggested remove google play updates and then reinstall and update everything, that was last night. it casually freezed more and then it seemed to sort of work better last night and this morning. and just a few minutes ago, i had a new pop up screen "Runtime Error bad argument#1 to 'abs' (number expected, got nil)" as google is one of my loyal and usually helpful friends i asked it, to my surprise i found basically zilch. putting "Runtime Error bad argument#1 to 'abs'" inside quotation marks was limiting results, it didnt look like other phone users had had similar troubles.
i did see this hit "http://geco.mines.edu/guide/Run-Time_Error_Messages.html" lightly scanning over it made me think i was not looking in the correct place. as the word "intel" was mentioned a few times.
i found another page "https://github.com/layeh/gopher-luar/issues/1" as the title is similar to my issue "bad argument #1 to <function name> (userdata expected, got string)"
those with far more of an understanding of android and code, please assist...
thank you

View attachment 4419367

More and unusual pop ups

nothing?
seems my phone has signed me out of google play
and has unrooted itself
many times the "Samsung UI has stopped working" pops up
i was hoping those with much more knowledge would have offered some suggestions.
i will back up all my data (in several different ways)
root my phone (again)
do a system re-format
and then re-install my apps and crap
crossing my fingers that that is all it needs... cause frankly i have no idea what, how, or why it recently crapped out. i suspect it was one of my apps, as the phone was working very well for several years, and within the last few days its all freezes and hangs, and occasionally crashes and reboots..

This morning I woke to find my phone looking like this

Related

my atrix locks up

i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
kga943 said:
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
Click to expand...
Click to collapse
Did you install any applications from the market? Is your phone freezing while a certain application is open or does it freeze even on the homescreen? If you have a lot of applications installed try to deinstall and look if it becomes better. If not try a factory reset. If it still freezes than return it for a new one.
Would you mind saying what you were doing when it locks up?
If it's during Music, it doesn't actually lock up, it just shows a black screen for about half a minute. Everything still functions, it just doesn't show.
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
I have a feeling there is a bad batch of units out there.
Try factory reset and see if it continues to lock up, if it does, return it for another.
kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sounds like a broken phone. Try a factory reset (if you return it they anyway ask if you did that) and if that won't help get a new one....
kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same thing happened to me yesterday, the light was very dim green and the phone did not respond until I pulled the battery. It hasn't happened again.
I've already had to replace my Atrix for another issue. Right now my confidence in this phone is not very high, but it is brand new. Lots of issues will probably pop up and be fixed via software updates- at least I hope thats the case.
It really feels like all the issues people are having with this phone are software related. Maybe motorolla will just cave and give us gingerbread with no blur
I've had the same problem while playing music...over the past 3 days after about 30 minutes of tunes it'll lock up and after another 5 reset itself...i've done the reset after the second and it still does it...i'm bout to take it back and exchange it...i expect glitches but damn.
Motorola Atrix (stock)
AT&T Fuze (Energy.RAPHAEL.21916.Sense2.5.Cookie.2.0.sencity)
I have had the issue happen 2 me twice in 3 days, the last time was when adding the note widget to screen. It was not completely locked up just the touch screen, i could press the power off button but the touch screen would not let me shutdown
something you might want to try if a factory reset doesn't work would be a reinstall from the recovery menu.
power your phone off
hold the down volume key and the power button
release the power button once the phone begins to boot
keep holding the down volume button until you see "fastboot" at the top of the screen
now be careful, the down volume button navigates through the boot options and the up volume selects one
so press the down volume button until you come across "android recovery"
once you see it press the up volume button to select it
once you get to the screen with the exclamation mark tap the bottom right of the touchscreen, this should pop up the recovery menu
select wipe data/factory reset
let the phone do it's thing
good luck
I've seen this resolve some audio codec issues that were causing the phone's mic to not work, dunno if it'll work for your issue but it can't hurt to try.
best of luck
bl4ck0ut
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
mrlinux11 said:
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
Click to expand...
Click to collapse
I have the same problem (screen randomly locks up once or twice a day, buttons dead) and have found the above "solution" to work perfectly, also. The problem however is that pressing the power button twice and unlocking the phone is not exactly elegant especially if the screen locks while you are trying to answer an incoming call.
I changed my battery settings to "performance mode" as I read somewhere that that might help. I will let you know if that seems to resolve the issue.
Changing battery setting doesn't seem to do anything. I still get my share of frozen/locked up screens a few times a day. Still have not figured out how to replicate the behavior. It really does seem random.
I've been suffering from this as well, I'm going to try to exchange my phone and see if that helps.
Exchanged my phone today. So far I haven't seen any locked/frozen screen issues. I am relieved. Maybe there are just a few bad units out there.
Also for what it is worth ... the lady at AT&T told me that taking out the battery while the phone is on would fix it. Since I never figured out how to replicate the behavior I couldn't verify that her suggestion would indeed actually fix the problem and demanded an exchange anyways.
atrix does lock up and have glitches
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
It happened to me as well. I had installed some apps but when it froze it had been off (the screen that is) so it was sitting then when I tried to open it by pressing the power button the green light came on but it would not wake. I removed the battery, replaced it then it did the same thing again (including the green light). I removed and installed the battery once more then it was fine. It must have been something in the backround but not sure as to what that was. Hasnt happened again though.
pedroosan said:
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
Click to expand...
Click to collapse
strange, skype worked for me... oh well.
did you ever find a solution for the lockup issue, have the same thing, very frustrating but not as frequent as you thankfully.
My Atrix started to freeze up when I undervolted the CPU using SetCPU and I would have to pull the battery out and restart it. I increased the voltage settings and it hasn't locked up since, so if you have undervolted your CPU and your phone is locking up, you should increase the voltages.

[Q] Stock 4.2.2 - Impossible to wake up, white flashing led

Hi,
Does anyone else have the same problem I have?
If I leave the phone running on battery for a couple of hours it is sometime impossible to wake it up by pressing the power button. Also the LED flashes white (not red). In order to get it working again I have to hold the power button a couple of seconds causing it to reset.
This happens on stock 4.2.1 and also in CM (4.2.1 and 4.2.2).
Seems like a HW problem? Should I send it in for repair?
BR/Svanteson
I've had this issue as well. It may be an issue with one of your downloaded apps. I have gone back to stock without any 3rd party apps and I haven't had the issue yet. Going to test a couple days and see what happens.
Edit: Maybe if you post some of your 3rd party apps you downloaded we can see if we have some in common.
Sure, here are some of my 3rd party apps
Moxier Mail
Eniro
Hitta
Wifi Analyzer
CPU Spy
Subnet calculator
Quadrant
Dropbox
Facebook
Whatsapp
Viber
Spotify
Shazam
MX Player
Truecaller
Llama
Android Lost
Out of those, Facebook and Android Lost are the only ones we had in common. I'll report back on this thread if this issue returns on my freshly flashed stock device without any 3rd party apps.
Similar problem here...
beand1p said:
Out of those, Facebook and Android Lost are the only ones we had in common. I'll report back on this thread if this issue returns on my freshly flashed stock device without any 3rd party apps.
Click to expand...
Click to collapse
Similarly, on two occasions now, I've gone to bed with the N4 on the charger, only to find it completely shutdown in the morning, and the battery unchanged from where it was when I plugged it into the charger. It required holding the power button down for quite awhile before I got a response and the unit rebooted. The first time, I didn't bother doing anything at all, but this morning, when it happened again, I called N4 support. I was advised to do a factory reset, and monitor it. If it did it again, they'll do an RMA. It seemed they would have sent another one right then if that's what I wanted them to do, but I told them I'd try the factory reset. They also sent an email with a direct contact link to the agent I spoke with in the event I need to return it.
My Device:
Nexus 4 16GB
Android 4.2.1
Kernel 3.4.0-perf-ge039dcb
Not rooted
I'll also post if the factory reset works. I've also read online, that holding the Volume Down and Power Button both for about 10 seconds, disregarding anything that appears on your screen, will shut your device down. Restart and, at least for several posters, the problem disappeared. Just an FYI. I'll try it if the reset doesn't provide the cure.
No joy....
Phubai said:
Similarly, on two occasions now, I've gone to bed with the N4 on the charger, only to find it completely shutdown in the morning, and the battery unchanged from where it was when I plugged it into the charger. It required holding the power button down for quite awhile before I got a response and the unit rebooted. The first time, I didn't bother doing anything at all, but this morning, when it happened again, I called N4 support. I was advised to do a factory reset, and monitor it. If it did it again, they'll do an RMA. It seemed they would have sent another one right then if that's what I wanted them to do, but I told them I'd try the factory reset. They also sent an email with a direct contact link to the agent I spoke with in the event I need to return it.
My Device:
Nexus 4 16GB
Android 4.2.1
Kernel 3.4.0-perf-ge039dcb
Not rooted
I'll also post if the factory reset works. I've also read online, that holding the Volume Down and Power Button both for about 10 seconds, disregarding anything that appears on your screen, will shut your device down. Restart and, at least for several posters, the problem disappeared. Just an FYI. I'll try it if the reset doesn't provide the cure.
Click to expand...
Click to collapse
Following up on my post yesterday, a hard reset did not help anything. Neither did an update to 4.2.2 for that matter. I also tried holding the Volume Down and Power Button until it shut down, and while the problem hasn't re-occurred, I really haven't provided enough time to tell yet. So Google is sending me another one and issuing an RMA. In the interim, while I'm waiting for the new one to arrive, I'll follow up if the VolDown and Power button has done anything.
I'm having the same issue. I just woke up, phone had a flashing white LED and would not boot. A reboot was neccessary. Is this a hardware failure?
The last couple of days I have not had WLAN activated. So far it is running fine.
I will activate WLAN today to see if the problem reappears.
svanteson said:
The last couple of days I have not had WLAN activated. So far it is running fine.
I will activate WLAN today to see if the problem reappears.
Click to expand...
Click to collapse
Why would you think there's a correlation between the two? I do have problems with wireless-notifications; for example, messages on whatsapp are often delayed, where I get a notification at say 11PM when the message was sent 10:45PM. Do you also experience this?
No problem noted this morning...
Phubai said:
Following up on my post yesterday, a hard reset did not help anything. Neither did an update to 4.2.2 for that matter. I also tried holding the Volume Down and Power Button until it shut down, and while the problem hasn't re-occurred, I really haven't provided enough time to tell yet. So Google is sending me another one and issuing an RMA. In the interim, while I'm waiting for the new one to arrive, I'll follow up if the VolDown and Power button has done anything.
Click to expand...
Click to collapse
I don't know whether holding the Vol Down and Power Button resolved the issue, but at least it didn't happen last night whereas it has been failing nightly when on the charger. Unfortunately, I was just notified that my replacement has already shipped, or I would tell them to hold off a day or two. For those of you experiencing this, you might try holding the Vol Down and Power Button at the same time until the device shuts down ignoring anything on the screen. Then simply restarting. I'm not saying that mine is fixed, only that it had a good night and that was the only thing I've done.
I will post again up until I have sent this device back. I have 21 days in which to return it or my credit card will be charged for real.
Phubai said:
I don't know whether holding the Vol Down and Power Button resolved the issue, but at least it didn't happen last night whereas it has been failing nightly when on the charger. Unfortunately, I was just notified that my replacement has already shipped, or I would tell them to hold off a day or two. For those of you experiencing this, you might try holding the Vol Down and Power Button at the same time until the device shuts down ignoring anything on the screen. Then simply restarting. I'm not saying that mine is fixed, only that it had a good night and that was the only thing I've done.
I will post again up until I have sent this device back. I have 21 days in which to return it or my credit card will be charged for real.
Click to expand...
Click to collapse
Mine also failed while on the charger a few times, but it also happened when not charging, so.... I'll try your solution. Why not!
This just happened again this morning. My alarm failed to go off, but the phone LED was flashing white. I could not turn the screen on. I did install some 3rd party apps yesterday:
Facebook
Tasks Free
reddit sync
Ally
IMDb
Pandora
Twitter
I tried the Vol Down + Power and that didn't work for me. I think I am going to RMA the device.
Yea...I have a few apps on my device, but not the ones mentioned here. So I don't think that can cause it. Hoping for more responses! I subscribed to this thread now.
Does anyone know if there is a bug report for this issue?
Not sure, don't think so as I've googled this quite alot. I just saw my telephone, which was idle next to me for about an hour, reboot itself. I saw the google and then the nexus logo without me even touching it. No white flashing LED this time, allthough that also has happened to me. This is getting very annoying now...
Google Support's reply on this
I have seen this happen to my phone more than a few times. I can't make it happen consistently though. I contacted the support hoping for a RMA, and today I received this response from them.
"Thank you for contacting us about your Nexus 4 and providing those details for clarification. This issue could be possibly not be a problem, it is a feature as with any Jellybean OS device; and goes in to the sleep state after some hours of inactivity - such as the details your describe when left overnight. It can go in to a deep sleep, where holding the power button for 30 seconds or more is what wakes the device up."
So this is a *feature*? It seems puzzling to me. I don't know if receiving a call would wake it up (if not, it would definitely be a problem).
I also tried different roms, PA and Xylon, and stock 4.22 with different kernels ranging from Franco to Motley. It would still happen. Rarely but it's still there. Also I am trying to see if changning the minimum clock speed to 1024 would change anything. I will report back once I have more info.
Still working so far...
I've not had a problem with mine since the Vol Down and Power Button shutdown. It may not even be related and may have just "healed" itself, or the problem has simply become intermittent and hasn't repeated itself yet...dunno unfortunately. Since my replacement will be arriving today, I may never know since I'll be shipping this one back to them. I may wait until Monday to ship it though, and see if it acts up again and repost if it does or doesn't.
Hopefully the replacement won't have this problem at all!
locked up
I don't think the flashing white-LED is a signifier of a problem. I think it is a different status message, like email or facebook, or something. I haven't found that documented anywhere, but I've noticed it is blue sometimes and white other times. Without being locked up.
My phone will lock up while charging overnight. I have turned off Dream State and the LED notifier thinking it was related to these. It did seem to be somewhat better after that, but the last two nights have seen the phone locked up.
Also, holding down the power button for 30 seconds will hard power it off at 10 seconds, it seems to me. That is typically how I deal with this lock up! Hold down the power button 10 seconds, release, press it again and wait for it to boot.
This is frustrating. I was thinking of rooting the phone so I can use a logwatcher, but I'm not sure I will see anything in the logs after booting the fracking thing.
But.. while I consider that I will start by uninstalling Facebook, Dropbox, and Twitter apps, based on seeing them on other people's lists.
I'm going to RMA the phone. Just a question, what charger do you guys use? I've been using a samsung charger (from my Galaxy S2), perhaps that's related? As it does happen while charging mostly, allthough I saw the phone reboot itself out of nowhere without it being plugged in yesterday too.
I've only used the Nexus 4 charger on mine. No others. I'm on my new device now but haven't sent the other one back yet. Probably tomorrow.
Sent from my Nexus 4 using Tapatalk 2

Phone will turn on but doesn't work

Hello, I was using my phone (Setup WatchOn and was playing with it, did not add or remove anything before my problems began) which I was able to use WatchOn without any problems, then after about a hour of not receiving any texts I suddenly received 6 in a row that didn't show up when they were sent. I restarted my phone since that was weird obviously and when it boot back up I can no longer do anything with it. I can turn on the phone (I have already restarted several times, removed the battery and put it back in) but when the phone is on I can't swipe up to unlock the phone. The time is displaying and the battery is changing like the phone is completely normal but I can't get into it anymore. If I hold the power button and spam press the restart button it actually react to it eventually but it takes some time.
If anyone has any idea what's wrong or how to fix it I would appreciate it greatly.
Try using the Samsung Kies restore method.... I have posted a couple of times on multiple threads on how to do this....
bmroczka said:
Hello, I was using my phone (Setup WatchOn and was playing with it, did not add or remove anything before my problems began) which I was able to use WatchOn without any problems, then after about a hour of not receiving any texts I suddenly received 6 in a row that didn't show up when they were sent. I restarted my phone since that was weird obviously and when it boot back up I can no longer do anything with it. I can turn on the phone (I have already restarted several times, removed the battery and put it back in) but when the phone is on I can't swipe up to unlock the phone. The time is displaying and the battery is changing like the phone is completely normal but I can't get into it anymore. If I hold the power button and spam press the restart button it actually react to it eventually but it takes some time.
If anyone has any idea what's wrong or how to fix it I would appreciate it greatly.
Click to expand...
Click to collapse

CQATest app on Marshmallow Causes System Issues?

Thought I would share this here - though I believe this is effecting other Moto models as well.
The Moto app "CQATest" seems to be the culprit with major instability issues I've had since the Android Marshmallow update. Before the update, my phone was so smooth and fast. Then the update came, and I blamed it on Marshmallow. Screen response to anything was very slow. Sometimes completely unresponsive. If i tried to touch a notification in my notification bar, it might be 5-10 seconds later before anything would happen, and the app would open. Sometimes it wouldn't ever open at all. Or when Facebook did open, it might take another 10-15 seconds before it went to the item it had notified me about. The camera in particular was slow to respond - with visible lag whenever trying to take a video - or would just crash. The phone itself got into a fairly normal habit of rebooting itself several times a day. And on startup, sometimes it would take 3-5 minutes before it would finally get to the home screen. Simply unacceptable.
So yesterday I started Googling for answers, and ran across a thread on Android Forums talking about issues people were having with CQATest. I immediately went and found the app in the settings>applications menu, under "All Apps" - force stopped and disabled it, then rebooted.
Guess what? The phone boots normally again! And the general responsiveness and functionality are back to what it was prior to the Marshmallow update. I couldn't be more pleased right now - because I was getting very frustrated with what is a relatively new phone.
I'd be interested if others have experienced something similar? Or are having similar lag issues and try this solution to see if it works for you.
Mods - if this CAN be confirmed, it really should be shared with ALL Moto users who've been upgraded to Marshmallow and have similar issues. The Android Forums thread user was originated by someone on the Moto X for instance.
Thanks for your time and feedback.
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
No apparent issues with anything else since disabling it that I can see. And yes, I'm on a DT2.
Zeljko1234 said:
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
Click to expand...
Click to collapse
I have had CQA Test disabled before and after Marshmallow and notice no misbehavior. I also have been using advanced calling since i got the phone on launch day and have never had a problem with the call quality as others have.
CQATest not causing problems on my Droid Turbo(1)
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
GeckoDad said:
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
Click to expand...
Click to collapse
My DT2 was suffering from slow-downs for a couple weeks, then suddenly had the random shutdown and power-only-on-charge scenario yesterday. I was getting ready to do a factory reset.
On one of the reboots, I had a notification about CQA test. When I acknowledged it, I got notifications that "CQATest wants to access this," and "CQATest wants to access that." I denied them all and started hunting up this app I'd never heard of. That's when I came across this thread. I disabled CQATest, but still had the problem. I then remembered that the "old" Amazon app had just updated. I force-closed it, disabled it, and now the phone is back to normal. I see no need for CQATest, so I'm leaving that disabled, but I firmly believe that the Amazon app was culprit.
EDIT: I may have typed to soon. The phone shut off randomly twice today, requiring connection to a power cord to bring it back to life. It does, however, remain powered up upon disconnection (for now?).:-/ I did not clear the cache after deactivating those apps, though, so we'll see if that does the trick.
..
Hi there.
Backstory: My DT2 is almost 3 years old. I already had to send it back to Motorola once for a camera issue, but generally I didn't have any major performance issues for the first year and a half or so. Then it started to decline. Namely OS was taking longer to respond, battery life declining. Then when it was about 2 years old it began the random shutdowns. For the last several months I haven't really had the random shutdowns, however, my battery has been pitifully horrible at holding a charge, and it will usually shut down before the battery indicator hits 0%. First it was around 15%, gradually getting worse. Now it often shuts down between 30-40%, especially if I haven't been on battery saver since disconnecting from the charger.
Now today, I ran down my battery within a few hours to about 30% and it shut off, which was not abnormal. However, upon connecting to charger and attempting restart, the battery indicator jumped from 30 up to 40, then down to 4. Got a weird screen before startup that looked like a system error screen and was afraid it was going into factory reset without my prompting it. Pressed the power key once briefly and the phone went into normal startup, but when it turned on, CommServer was stuck in notifications bar and battery indicator was stuck at 3%, similar story to the others in this thread and others.
I disabled the apps suggested by GeckoDad, and so far the phone can operate, but I've had it plugged in for maybe 30 minutes and it's still hanging out at 3%. Was planning to get a new phone soon, but had hoped to wait another month or two... Probably going to head over to Verizon this afternoon to see if they have any suggestions to keep my DT2 alive until I'm able to replace it.

Startup Keypad Lag Issue

Hi to all from a 99% highly satisfied v20 user!
I have run into an intermittent issue with my Verizon v 20 (VS99513A).
ONLY when I initially power-up the phone, do I sometimes (often enough to be a nuisance but far from consistent) get a significant lag on the "Secure start-up" page of the keyboard appearing where I enter my passcode. There have been a small handful of times that, no matter what I did in terms of waiting or tapping, the keyboard would not appear causing me to do a power-off/restart which always cleared the issue.
Most of the time I wait until the screen flashes a brighter light before tapping ( just a few seconds) and (most of the time) the keyboard appears. It will also appear frequently on its own if you just wait long enough.
The problem is the inconsistency of the keyboard not appearing reasonably quickly so I can enter my passcode and go on with my life's journey at that point!
I have chosen NOT to use the fingerprint entry system for a number of reasons and prefer using the above system.
My one desire is to have the keyboard appear as quickly as is reasonably possible and do so consistently.
Other that that specific issue, I love this phone!
I did search for this issue and did not see anything approximating it. If I missed then please accept my humble apology for any duplication with this query.
Bootup times can vary. And with Verizon bloat I'm sure it is wildly more inconsistent. I rarely.run into this issue, but I also rarely reboot my phone. Perhaps a cache clear might help? Don't know what else to do besides factory reset but sure you don't want to do that. I just rooted my phone and haven't noticed any performance issues aside from battery life seeming worse. Not related to root though as i updated to 10j Sunday, rooted last night and hoping battery life goes back to what it was on 10d.
Just for some clarification, what do you mean by power up? Is it turning the phone off completely and restarting it or just clicking the power button ( or double tap the screen).
If its a boot up, then its usual normal to have the keyboard take a moment to pop up due to everything loading
If its the second then try using a different keyboard or factor resetting the phone
Robdudem said:
Just for some clarification, what do you mean by power up? Is it turning the phone off completely and restarting it or just clicking the power button ( or double tap the screen).
If its a boot up, then its usual normal to have the keyboard take a moment to pop up due to everything loading
If its the second then try using a different keyboard or factor resetting the phone
Click to expand...
Click to collapse
"Is it turning the phone off completely and restarting it..." Yes, that is the only time(s) it happens.
I grasp the idea of "loading" but cannot (equally) grasp the inconsistent amount of time that it takes for the keyboard to materialize. The few times where no keyboard appearing leading to a reboot deepens the mystery for me.
If the extended loading time is due (largely) to verizon bloat, is there a safe way to rid oneself of as much of it as possible?
harryzee said:
"Is it turning the phone off completely and restarting it..." Yes, that is the only time(s) it happens.
I grasp the idea of "loading" but cannot (equally) grasp the inconsistent amount of time that it takes for the keyboard to materialize. The few times where no keyboard appearing leading to a reboot deepens the mystery for me.
If the extended loading time is due (largely) to verizon bloat, is there a safe way to rid oneself of as much of it as possible?
Click to expand...
Click to collapse
Of course, you can disable the apps by going into Setting>General tab>Apps. From there you just find the Verizon apps and disable as much of them as possible. Which stops them from booting when you restart.
One thing to keep in mind when powering up the device is a few programs want to start up at the same time (like your wallpaper, getting signal from service provider, loading the apps on your screen, loading widgets, etc). Which causes the keyboard to be pushed but back in a queue. Happens to me all the time, but I only restart my phone once every week and I give it a moment for everything to be settled in.
Robdudem said:
Of course, you can disable the apps by going into Setting>General tab>Apps. From there you just find the Verizon apps and disable as much of them as possible. Which stops them from booting when you restart.
One thing to keep in mind when powering up the device is a few programs want to start up at the same time (like your wallpaper, getting signal from service provider, loading the apps on your screen, loading widgets, etc). Which causes the keyboard to be pushed but back in a queue. Happens to me all the time, but I only restart my phone once every week and I give it a moment for everything to be settled in.
Click to expand...
Click to collapse
This^^^^
Sent from my LG V20 using XDA Labs
To All,
My issue appears to have resolved itself if I restrict my tapping to the vertical blinking cursor on the left end of the entry line.
Tapping ONLY here consistently brings up the number pad.
Previously, tapping just about anywhere on the screen would bring it up.
Problem solved.
Thanks.

Categories

Resources