Hey everyone, I'm a fairly new OPO user myself here as well; I received mine back in early-mid October, and have had it since then.
But oddly enough, for the past two weeks or so, the following issues have surfaced and has become more frequent, and prominent than ever. For all the fellow OPO-users out there, I was wondering if anyone else has come across the same issue(s) that I've been going through... Unfortunately I really haven't had the time to look up any solution methods and whatnot with two young'uns whom are extremely demanding of my presence... All. The. Time.
So I thought that if I compiled my little list here, hopefully some kind soul will reach out to me with answers (or at least, the direction to where I could find those answers) and make my day just -that- much lighter.
Now just to mention the main points : NO, I have NOT rooted my phone, and YES, I DID install the OTA update, and currently my CM version is the 11.0-XNPH38R.
~~~~~~~~~~~~~~~~~~~~~
a) sometimes, my OPO screen will absolutely REFUSE to turn back on, after I've put the phone to sleep. nothing i do can get the screen to turn back on again - unless it decides it finally wants to. (it's got a mind of its own, this thing... and it's just as stubborn as I am. UGH.) i try double-tapping the screen several times (i've turned that feature on) and i try pressing the power/wake button, or holding it down, ... but zilch. this will usually last up to 10~15 minutes. (after 5~10 minutes of trying to bring it back to life, I just give up and let it be.) when the screen DOES end up turning back on, it's either flashing the "power off/reboot/accessibility" menu several times (probably from me trying to mess with the physical power/wake button) then finally respond to my 'backspace' on-screen keys, or the home icon, returning me back to the proper lockscreen it's supposed to show. ANOTHER way it ends up FINALLY responding, is that the phone will vibrate in short sequences of two, maybe three times and then it will initiate the rebooting process. then everything starts working fine again. i don't recall having ever done anything to trigger something like this to happen, either...
b) the keyboard (the stock Android keyboard) randomly will NOT work; by that I mean, when I am in a messaging app, or any other app that requires a person to TYPE WORDS ON, the keyboard DOES show up, (along with the suggestive bar just above it) and when I try to type, all the usual things will occur; the letter I happen to press will pop-up in response to my tap, and in the suggestive word bar above, it will start showing me the possible word combinations possible based on the sequence of the letters I type, but nowhere do I actually SEE on the SCREEN/message bar/etc. any letters or characters popping up. this issue too, will happen out of nowhere and will last about 15~20 minutes as well. usually what fixes the problem (as annoying as it is) is if I shut down/turn on, then reboot the phone a couple of times to get the keyboard to actually start working again. but there MUST be an easier method to fix this (and all my other issues) !
c) the stock camera app; this issue actually started occurring within days - just under a week of actually getting the shipment of the phone to my place. I was testing out the camera functions, the usual, then suddenly, I would get booted out of the app, and a message saying "The Camera cannot be used at this time" will pop-up as a result. (although, what was even STRANGER, was for a while, (for about 2-3 days) I was receiving a totally different message that didn't even make any SENSE: it said something along the lines of "the camera could not be connected to the device at this time" or "the camera has been disconnected from the device"... i don't even know HOW a camera can "disconnect" itself from the phone, but apparently it CAN.) with this issue, there was absolutely NOTHING I could do to start making it work again. it was non-functional for three, four days straight (no word of a lie) then just for the hell of it, I decided to open the camera app again, and boom, it was working. that didn't last long, though... then suddenly after opening the camera, there would be a prolonged black screen on the phone that wouldn't go away, and I couldn't select any options whatsoever... then when the camera finally started "working", i tried taking a picture - i thought that it would work, since nothing was indicative of it NOT working... but alas, such was not the case. when i went into gallery, to browse through the photos I had taken, they were not there at all, and the photos i had thought were taken weren't actually taken at all.
Asides from that, and some occasional (frequent) crashes while using the phone, I'm not feeling too frustrated by it. (I guess I just have an effin'-load of patience.) Still, I would greatly appreciate any thoughts or suggestions about this dilemma of mine, or providing me the key to all of the answers to these stupid bugs.
Thanks for all those who took the time to read my lengthy post. :fingers-crossed:
-- MK.
Related
Ok, so far I've dumped the ROM and uploaded the kaiser-HardSPL and all was going lovely. However, after most of a day of pretty much inactivity I find the device suddenly goes very slowly. By which, I mean it can take several seconds to draw the screen.
Thinking this might be a rogue application using up all the processor cycles, I poked it up the bottom with the stick. (While doing this the first time, I held in power and camera just to see the boot loader text, but then I did it again with no buttons held.) It's a Vodafone device but it sat on the Vodafone splash screen for about 2-3 minutes then spent longer than that on the Windows Mobile screen before eventually dropping me into normality.
Except it's incredibly slow normality - I clicked on "start" and after a minute, it's not done anything yet.
Next step is a hard reset unless anyone has any better suggestion?
Help!
I assume you've pulled the battery?
Never assume anything... The full answer is, "No, but I have now"... I'm not sure that's going to do anything more than a soft (poke up the bottom) reset though. I'm now just waiting for the splash screen to subside while I'm typing this.
Having left it half an hour, while it went into standby and after noticing that the clock had stopped updating, I'm of the opinion that the already slow device has got slower...
Ok between 1 and 2 minutes to move from the splash screen to the "Windows Mobile" screen.
Now there's a turn up... After a further minute or so, I get a message, which has now cleared and gone back to the "Windows Mobile" screen before I had chance to copy it here. Basically it said that it had failed to boot either because I'd turned it off improperly or I'd installed something that it was opposed to. I should press send (I guess the green button) to reset to manufacturer's defaults.
Since that's my next stage anyway, I'll re-poke it with the pointy stick and press 'send' when it pops the message up. I'll put my trusty old Nokia N73 into flight mode and take a picture of the message so I can transcribe it here for everyone's amusement.
More news as it breaks.
I've now hit the 'send' button so it's doing a hard-reset. Meanwhile, here's the text it showed me:
Code:
The device is unable to boot be-
cause either you have turned off
the device incorrectly or tried to
install an application from untrusted
source. Press SEND to reset your
device or press any other button
to cancel. This operation will delete
all your personal data and restore
the device to its factory default
settings.
Nice. Ok, I'm at the 'tap the screen to set up your device' screen now.
Wonder what triggered all that nonsense then...
If you're like the rest of us and tooling around the all the fun programs in this forum, there's no telling.
I tell folks on computers, "Every piece of software you put on a machine is a liability to the operation of that machine." We can say that applies to this nifty little devices too.
I've had my phone experience the same symptoms you have posted here. Luckly for me a battery pull fixed mine. Sounds like the luck didn't spread much. Sorry.
Keep at it though. And don't fret the crashes. They do happen from time to time when you play hard.
So, a hard reset and a restore of a backup (Yes, I made a backup a few days ago even though I've been in the trade 20 years!) later, I'm back to normality. All I've done that's weird is install pof's loader and I can't see that's anything to do with it. What I was doing at the time of the slowdown was trying to connect to the wifi network at work. I thought the networking had just got itself tied in knots somehow but as the machine was even mega slow to boot, I can't really see that. At least I can still get back to square one at the moment.
I just need to create a .nbh out of the rom parts I dumped yesterday so that I can recover from anything more major...
Meanwhile, if you do a 'boot loader reset', would you expect it to say 'serial' if the USB isn't plugged in?
I'm starting to wonder if there is a major bug in the WiFi of the Tilt. There are some other threads on AT&T's site about this, and my work with WiFi on this unit has been dicey. Hmmmmm...
I just started having this "bug" yesterday. Basically, what happens (randomly) is that when I press the power button, remove the stylus, or slide the phone open to wake it up I'll be met with a black/blank screen. The backlighting will be on, and the phone is responsive (can receive messages, make calls, sounds/notifications work), but I won't be able to use the screen. If I use the power button to turn the screen back off and wait a few seconds, the screen might start working again. This is completely random and I cannot duplicate it with any guaranteed process, but it seems to be when the phone is waking up from standby. After a soft reset, probably half of the time I'll be met with this same delima, which leads me to believe it's hardware and not completely software.
At the same time the phone is also struggling to re-paint the screen from the change of Landscape-to-Portrait and visa versa. Also opening and closing windows to get back to the today screen also cause a problem. I've disabled TF3D to see if that makes a difference, it doesn't. I have a blank today screen with no plugins to free up the system resources, and am still having this issue.
I'm using JD's Rom (probably around 1.3, it's been running fine with no issues up to this point).
I'm also using S2U2 1.35 (if that makes any difference, haven't had any problems until recently)
The phone has never been dropped, it's in InvisibleShield, and normally sits on my desk charging all day.
This started happening last night for no apparent reason and it's really starting to irratate me.
Any advice is appreciated. Thanks.
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
After more testing..
After some more fiddling around with the phone I'm about 90% certain it's a hardware issue. I noticed that when I slide the keyboard out if the slide portion is past the number line then the screen will stay on, but not update. I don't know how well I can explain it. If I'm typing and hold the screen to keep it from opening all the way then I can see the letters/words appear (in txt msg/email), but if I let the screen goes and it slides all the way open then the screen will stay on and only show what has already happened, any more typed characters will not appear, but if I move the screen back to the number row then the screen will re-draw and update what has happened.
Is this something that Sprint should fix no questions asked?
lulugirl896 said:
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
Click to expand...
Click to collapse
The last piece of software I installed was Gyrator 2 on Friday-ish. Thinking that it was the problem, I removed it using MemMaid. I'm going to give the phone a flash tonight and see if it is software related (hoping for the easy fix) but as the post above says, I'm almost certain it's a hardware issue. I just wish I knew how it happened. . . So much for that time putting those InvShld on.
Final Update (this can be closed)
I took it into a Sprint store and they replaced the "flip" on the top for free (I have insurance).
Point of the story/thread, this can be closed, it was a hardware issue, and now it's fixed.
I encountered my first problems with my Nexus 5, which i am very happy with, about 1-2 weeks ago. After about 11 months of happy, problem free use, without dropping it or anything else, it started misbehaving (about a month with Android L so far). It crashed and wouldn't start up farther than the 'android' screen most of the times. Rarely it would fully boot, but the seemed to go into the lock screen and crash after a max. time of about 1 Minute of normal use. After going through this a few times I checked some forums and found a solution suggesting to repeatitly press the lock screen button while it boots. This solution worked quite good, even though i had go through the process multiple time the following days.
Last thursday evening (today is saturday) though my phone crashed fully once more (just after checking and having an 80% charged battery) , but now the quick hits on the Power button did not work at all. Instead my phone wouldn't react at all. Neither pressing the volume rockers alone or together with the power button would work either. Having plugged in the Nexus though acheived it to at least reach a state which seems to be a more common problem. It has been discussed and solved for many (seemingly everyone) in another thread called '[Q] Nexus 5 constantly rebooting at 'Google' ' (Link to this at bottom). Long explanations and videos of the situation have been given here, depicting my exact situation along with two solutions:
1. Using magnets near the power button (to apparently loosen two magnets used when pressing the power button)
2. Two flick and quickly press the button (for some this had to be done many minutes)
After seeing many (surprisingly) positive reactions to both methods, I tried them myself. I began with the magnet method and without having it connected to a charger it would boot to the google screen twice (note: As said, without a charger nothing happened). First once about as long as when connected to power and once very briefly. This method didn't prevail more than once and i couldn't start it up any diffrently than before.
So next I tried the flicking method and (maybe because of the magnets) it booted al the way to the 4 colored dots flying around. I let go and it crashed once more. I fooled around with the magnets again and tried the flicking method again, without stopping, as other users mentioned a long time needed (15-30 Min.) and after about 20 Minutes I stopped. My Nexus did not crash, but it is now 'stuck' at the colored Dots. I have tried connecting it to a power outlet, my PC and again started pressing the power button and volume rockers, without effect. It has been so for about an hour if not more. I will try to drain the battery and then continue, but if any other solutions are known Please help, thank you!
Link to other Question: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-constantly-rebooting-google-t2809617
Update
After having drained the battery completely and then charging it again, the normal 'charging battery' icon popped up. Trying to start the phone, however resulted in getting into the flying dots loop again... I am able to go into fastboot mode, but neither start or Power Off help the situation. Should I go into recovery mode? I would strongly dislike losing all my data....
(Update)
I tried going into recovery mode, but the only thing that happened was that a little android figure, lying down with a red exclamation mark showed up (which should be normal as I recall going into recovery mode before my problems), and a text saying 'no command' above it. What now? I'm all out of ideas and back up plans, except calling google as it should still be under my warranty. But I don't want to give up my data as I haven't saved anything and I don't want to give up my phone either.
This is kind of a last resort - to see if anyone has any experience with this problem. I have Googled around for similar problems and haven't quite found the same issue anywhere.
OK, so let me emphasise, this is not a bootloop - there is clearly some kind of hardware or firmware problem where the phone is interpreting the power button as being pressed.
I can power on, and the phone will get to various points before then rebooting, as though the power button were being held down:
- often it only gets to the splash screen and then reboots
- sometimes I can get it into recovery, but whatever option I happen to highlight (I have about a second or two to do so) just gets selected as though the power button were pressed
- sometimes the phone will even boot and can be used for a little while (enough even for me to back up the files off it), but sooner or later a message will pop up saying something along the lines of "Continue holding power button to reset", again - OBVIOUSLY the system thinks the power button is pressed down.
The problem happened while the phone was under guarantee, the repair place kept it for weeks, eventually "replaced the motherboard" (so they say) and it seemed to work for a time. Now the problem is back and there is no more warranty. A reputable repair place has had a look and said they can't do anything.
I have tried taking the top cover off and fiddling with the microswitch (only thing I could think of) to see if there is anything obvious going on there, but that doesn't seem to be the cause of the problem.
Any ideas, before we ditch the phone as a $XXX loss?
Just to update - I managed to catch the phone when it wasn't going crazy, go into fastboot and flash CM10.2. Could've restored to stock I suppose, but I am concerned that may somehow have been the cause of the problem in the first place.
As of 12 hours later the phone is behaving itself. Can't be sure a new ROM is what did it, but fingers crossed...
I've gotten no help from ZTE themselves - they want me to do a factory reset and didn't even bother to read what my problem is. This is with the stock ROM for a ZTE Blade 10. I touch the power button and the screen doesn't stay off, instead turning on every time I move it (in the same vein as a "Lift to Wake" problem). This burned a huge hole in my battery the first day I had it, butt dialed a couple of people by opening my Contacts on its own, swiped important notifications away (including texts and reminders), and played with apps. I've managed to stabilize it some by tweaking some settings, but I haven't found a setting that disables this entirely.
I have screenshots of my settings in a second post, since I'm not allowed to post them in the original post.
Worth noting is that I have a custom lockscreen app, HiLocker, for which I set a five-second timeout. It does not seem to be the app, since the problem still presents itself when I disable it. Ergo, I either have to choose between changing that to instantly locking (thus making me enter my pattern again when my screen times out, even if I'm in the middle of using the phone) or keeping as is and dealing with this problem. I don't want this to be a choice. I want this five-second thing, but I want the power button to be absolute and keep the screen off until I push it again. My phone doesn't seem to understand something so basic: That's what the power button is for.
Does anyone know if there's a solution for this? Any pointers would be appreciated, thanks!
I hope this works.
https://i.imgur.com/uwdn8V5.png
https://i.imgur.com/aqd16Ko.png
https://i.imgur.com/RuhrvAV.jpg
Bump. Seems I can do that every 24 hours, and it's on the bottom of the page, so...
Still seeking any feedback. Anyone have any idea, or do I need to flash a ROM for the first time in half a decade?
One last try... can anyone help me?