Seriously, now battery status wont even run...
I go to open it, and it doesn't do anything, sometimes comes with a blank screen and freezes, other times I can get the options to show, but the POS won't take the options I give it...what the f***?
Related
every now and then, my screen seems to not be responsive to my touch. ill tap on an icon or widget to open it repeatedly with no action to take place. its like im 'not' touching my screen. it gets real annoying when it happens on the lock screen and i cant even access my phone for some moments till my epic decides to detect my touch. another issue ive been having with my phone is when i tap my screen, the orientation or something seems off. if i tap on something at the top of my screen it'll click something on the bottom or vise versa. these screen issues seem to be the major probs im having with my phone. ive tried to search all over the net to see if others users have this prob to see if its an issue with the phone in general or just something with mine. i havent found anything on this issue that im having. if you also experience problems like i have please let me know and/or if there is a fix or something i can do to remedy the problem.
*my screen issues are not all the time. its all random. /// other than that i LOVE my new phone and couldnt be more than happier to finally get rid of my iPhone after 2.5 years.
Anyone else have issues with drawing a pattern to unlock your phone? over half the time, when I try to draw the pattern, it will only pick up half of what I draw. If you keep trying it will keep doing the same thing. Only fix is to shut the screen off and then turn it back on again and then it will work. Anyone else experience this "bug?"
I'd be willing to donate if someone could fix this. It's annoying as hell.
EDIT: I've experienced this on completely stock DI18, EB13, EC05. I'm about to the point where I don't even want to use it anymore but I would like to have some security feature to lock it. I'm currently on the stock deodexed NOCIQ ROM with DStars clean kernel.
Never had that problem but I hate that unlock screen. PITA to unlock while walking.
Pin for the win
Sent from my SPH-D700 using Tapatalk
blazinazn said:
Anyone else have issues with drawing a pattern to unlock your phone? over half the time, when I try to draw the pattern, it will only pick up half of what I draw. If you keep trying it will keep doing the same thing. Only fix is to shut the screen off and then turn it back on again and then it will work. Anyone else experience this "bug?"
I'd be willing to donate if someone could fix this. It's annoying as hell.
EDIT: I've experienced this on completely stock DI18, EB13, EC05. I'm about to the point where I don't even want to use it anymore but I would like to have some security feature to lock it. I'm currently on the stock deodexed NOCIQ ROM with DStars clean kernel.
Click to expand...
Click to collapse
I had a similar problem for a while, except that it happened whether the phone was locked or not. Took it in and sprint said that touch sensor was defective, replaced the screen and it was good as new!
blazinazn said:
Anyone else have issues with drawing a pattern to unlock your phone? over half the time, when I try to draw the pattern, it will only pick up half of what I draw. If you keep trying it will keep doing the same thing. Only fix is to shut the screen off and then turn it back on again and then it will work. Anyone else experience this "bug?"
I'd be willing to donate if someone could fix this. It's annoying as hell.
EDIT: I've experienced this on completely stock DI18, EB13, EC05. I'm about to the point where I don't even want to use it anymore but I would like to have some security feature to lock it. I'm currently on the stock deodexed NOCIQ ROM with DStars clean kernel.
Click to expand...
Click to collapse
I had a similar problem, but found a way around it. I removed my pattern and downloaded an application called "AL II" by 'SmartDog Studio'. It's a security application that basically tricks any app you want into believing it's force closing, and in order to get it to work, you have to perform something. It's kind of hard to explain it in words, but i'll try my best. I downloaded the application, and opened it. Once opened, I chose 'Messaging' for the sake of this explanation. So I selected messaging and hit "protect". Once it says the application is protected, you just hit the menu button and change the settings to how you want. I personally chose "Rotate motion" for my selected unlock method. Basically what happens at this point is if someone picks up your phone and tries to read your messages, the application will force close (and will continue to do this forever until you perform the selected unlock method). With the "Rotate motion", you just allow the force close dialog box to pop up, then you just have to rotate your phone to have your screen facing down, then rotate it right side up again, and the force close dialog box disappears and you're back in business. There's other options you can choose such as, when the force close dialog box pops up, instead of selected "force close" you can tap on the text body of the pop up either 2 or 5 times (whichever you chose for it) and it will unlock your phone that way too. Basically what you're doing is tricking whoever picks your phone up into thinking your phone is a complete piece of garbage and they'll put it right back down because nothing will work for them. I hope that wasn't too confusing. If you wanna know more about it, just shoot me a PM and i'll be glad to explain it in more detail.
Zeke.
I've used had my Ouya for a few years now and today it just locks up. I get static audio, vertical lines, and lockups. I took the Ouya out and I noticed it is super hot. The fan only kicks on for a second during boot but never again... so it just seems to sit there and fry.
1: That fan should be kicking on.
2: It only locks up when I do certain things. Like Search, Factory Reset, nagivate menus, do stuff. If I just let it sit there, it typically won't lock up, but has.
I am kinda at a loss. I am thinking of reflashing another rom on it to see if that works. It boots up normally just locks up after about 10min. I am having problems with getting ADB working. When I connect it, it connects as a Media device MTP but no ADB driver being requested. I also cannot see the device with adb. I've tried the sysrq+Alt+i methods but it just reboots to a black screen with a ! on it. Doesn't really do anything from there.
Any suggestions?
The other day I was using my att s4 active and it went off on me. I put it in recovery mode and it just keeps going off. I don't know for sure but I vaguely recall installing a custom rom a long time ago. I've replaced the battery and charged it so I'm sure that's not an issue. Occasionally it will come up with an ! saying the software is not for the phone, take it to att. Other times it will boot up and will stay on for like 5 seconds, just enough to pass the lock screen.
Sometimes it sticks on secovery boouing (weird) and yet other times it won't do anything. I'd really like to get my pictures off of the phone.
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.