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...
[Q] HTC Desire "appears" as if it has the home button stuck, since a recent update
One of our HTC Desire is exhibiting very weird behaviour since a recent update (couple of days ago). It only affects one of the phone, the second one is working fine, both were updated within the same day.
** I will try to post the software version on the next post, I think it's triggering the "No outisde link for new user" error, even though there is no outside link!
This phone only started playing up about a day after the update, not immediately. It sometimes wake up on its own and bring up the "Recent Apps" screen, as if you have long-pressed the Home key. It then switches wildly between that screen and the zoom out (helicopter view?) view of all the home screens. Initially I thought it is hardware problem and the phone is 'screwed' but I think it's more software problem, since it can work normally sometimes.
The wild screen switching made it impossible to use the phone and because it is working constantly, it gets hot and drains the battery. The problem started to get worse when we plugged it into a PC to sync and it started to go crazy. Since the screen switching so wildly, I can't get into the menu to soft reset or turn off the phone properly. So had to hard reset it, and done that more than half a dozen times.
We did have an issue when we first downloaded that recent update, both phones didn't have enough space, so the install crashed out. We freed up more space and both phones appear to have installed the update fine. Well, until a day or so after, one of the phone started playing up.
At the end, I found that if I held down the optical cursor button (very hard work), it seems to hold off the wild screen switching. I can then sort of use the phone as per normal, so that I can join WiFi and change settings & install apps etc.
I noticed that the Rosie Utility is always showing on the "Recent apps" screen. I've never seen that on a normal "Recent Apps" screen before. Not knowing what it was, I googled and learnt that it's the SenseUI. I then compared the SenseUI info with AppKik and the crazy phone is showing a different size 1.9MB (laterly 2.0MB) whereas the working phone is showing 3.0MB, althought both said HTC Sense Version 1.0 com.htc.launcher.
So I figured something must have gone wrong with the SenseUI Launcher and hence it's doing crazy thing. So I downloaded couple of other launchers, LauncherPro and ADW Launcher. They initially seem to work then all of a sudden the crazy screen switching will start and they will get worse. It seems worst if I left it on the main home screen, if I was in an App, it sometimes stay calm for a while.
In frustration, I thought I will backup my SenseUI (rosie.apk) from the working phone using Appkik and then install it on the faulty phone, but the install failed. Probably because it's being used. Tried switch the default launcher to LauncherPro, still the same. May be it needed Root access to replace? So I rooted the phone with UnRevoke3 (after a long struggle getting the correct ADB working) but still can't install the rosie.apk.
Anyhow, after rooting the phone, it mysterously settled down. I could use the phone normally for quite a while, then it started again. Although not as crazy and only intermittently. Haven't used the phone later part of today, so not sure what it's doing at the moment. When I tried the phone this morning, I stumbled across an option to un-update the senseUI, so it's now supposedly switched back to the factory default (Eclair 2.1??) version? The info from Appkik is stil lthe same though.
My question to the experts are ...
1. Can I 'update' just the latest Rosie.APK since the phone update said I already got the latest and no more updates available. ? If so, where and how?
2. If not, can I download a working copy of Rosie.apk from somewhere, and how do I write that over the existing 'possibly' faulty version?
Any help will be greatly appreciated.
HTC Desire "appears" as if it has the home button stuck, since a recent update
Attached is the TXT file containing my HTC Desire Software Version details.
For some unknown reason, it won't accept my post if I had the text from this file in the body of the post. It keeps bringing up the error about no 'outside' link for new user.
Update: If I "Cleare Default" on SenseUI in the App2SD settings, then it appears to stop the Screen Switching, but the Home button stops working altogether, the rest of the home screens appear to work normally though. Very weird. I think the problem is definitely to do with corrupted Rosie.apk (com.htc.launcher) .
Hi,
In case it helps anyone else, my home and menu button on an hd desire became intermittently broken in that they would stop working for days.
I followed this and did a clear data on the rosie utility and they work fine now.
Whoop whoop!
Hey guys,
Had my transformer for 2weeks now and loving it. However recently (first noticed it 2 days ago) the notification bar has randomly started opening itself. It doesnt happen on a regular schedule -sometimes it will happen 3 or4 times in a couple of minutes, sometimes only once or twice an hour but not less often than that.
It happens even when im not touching the tablet at the time so i dont think the screen accuracy/calibration would be causing it.
I have turned it off and off a number of times to no avail and Ive also tried a factory reset and even with no additional apps installed it still happens.
Finally ive tried it both with and without sd card in and it happens in both situations.
Oh, and the dock connector being attached or unattached doesnt stop it either.
Has anyone heard of this happening before and or have any ideas to solve this problem?
i get this too all the time. i'm not touching the screen and the notification pops up for no reason. sometimes apps open up randomly too, for example i get an email notification and the email app opens. very annoying when plugged into a projector whilst giving a presentation.
somebody must be able to help. I'm not rooted by the way and have no intention too.
Sounds like a hardware problem - the touchscreen registering fake touch events. Check for mechanical stress in the lower right corner.
Update
I probably should have added, like yours mine isn't rooted.
I also turned on the developer options for touch detection, and it's definitely detecting "phantom" touches in the bottom right corner so definitely hardware not software issue.
Unfortunately, yesterday I started having issues with the touch screen being unresponsive in the right third or so of the screen, so I've called Asus this morning and am RMAing the tablet anyway.
I'd suggest you do the same rob if it's still in warranty, in case its a prelude to larger issues like mine was.
interesting thanks both. i was weighing up an rma because my keyboard dock is getting very loose, letting the top of tablet move about an inch without hinge moving. i've turned on show screen taps and already seen one. thanks again.
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.
My z-flip3 5g has a strange problem. If i close it (by folding the screen closed), then after opening (unfolding) the screen and touching the right side button/fingerprint reader to unlock it, i hear the quiet "click" noise that indicates the phone is unlocked, but the screen stays black. i then have to repeatedly push the lock button on the right to lock the phone again and unlock it again. after several attempts the screen finally turns on. sometimes it will go black a few seconds later and the same issue continues. but other times the screen will stay on and work fine.
i have noticed that if i do not close the phone (folding the screen together) then i do NOT encounter this issue. the phone screen turns on when pushing the right side button (or touching the fingerprint sensor) and everything works fine.
this issue started yesterday, a system update installed yesterday as well, could it be related?
i already restarted many times, booted into recovery mode and wiped the cache. nothing has helped. the only way to avoid the problem is by not closing (folding the screen shut) the phone.
One UI v 5.1
Android 13
Security patch level Feb 1, 2023
fully stock/not rooted
I have same behavior. Did you solve this problem?
Unfortunately no. Did a factory reset, hoping that would help, but the issue persists
Mine has recently started doing the same. Last update was right before this started several weeks ago. I don't have mine set to require fingerprint, it should just turn on after opening. If I open it partway, it will turn on, then turn back off when fully opened.
hi,
i have same problem, it's software problem?
Not completely sure about that. They update this thing so often, it could be coincedence that it started shortly after an update. I want to try blowing out the hinges as I've got some dust under there that I hear when opening the phone. Definitely not a phone to put in your pocket after working in the wood shop!
Digital Dragon said:
Not completely sure about that. They update this thing so often, it could be coincedence that it started shortly after an update. I want to try blowing out the hinges as I've got some dust under there that I hear when opening the phone. Definitely not a phone to put in your pocket after working in the wood shop!
Click to expand...
Click to collapse
and don´t take it to the beach either!
What is also strange is that when I close the phone and open it a few seconds later, there is no issues whatsoever. However, if I leave it closed a few minutes, then when opening it, the problems with the screen staying off happen.
Yes, definitely don't take it to the beach!
@netridah , mine is doing exactly that. Which makes me wonder is it a wake issue, or a mechanical/sensor issue with the hinge.
one more to the bill
I checked the flexes and I warmed up the logic nothing works
I have the same issue: Flip 3 - 5G with OneUI 5.1 - 1 April Patch level
When I open the phone I eventually see for less than one second the lock screen, the goes black and unresponsive.
Then I have to press the button to turn the screen off (even if it is already) and then re-press the button or use the fingerprint to turn it on and it will work (eventually, sometime I have to do it a couple of times).
I already googled it on many forums but no solutions, I've tried to:
Disable the always-on display - no result, at first looked like it did the trick but the day after was having the same issue.
Check all the updates of the system components like always on-on display (settings --> lock screen --> always on display --> info), no help everything is up to date.
Hi,
I have the exact same problem, only difference is that I'm on the z flip 4.
I get the black screen and sometimes when opening or closing the phone the screen can flash in a bright yellow or green color.
I got a motherboard but the problem continued
Next step changing screen is very expensive at the moment
This is driving me crazy - also started the day I updated to OneUI 5.1.
Hoping for a solution soon!
I am also encountering this problem, I went to samsung repair shop 1 month out of warranty, sales person said it is a screen issue and needs to be replaced for 430$. Mine was before the update, i took mine near the pool, got wet maybe, as the alarm for usb charging mentioned unplug it immediately, day after it began randomly dark when phone is openned fully. Zflip 3
Oh just an update, i did some tinkering today, Good lock all updated, disabled clockface, sprayed some contact cleaner on power button, and hinges, fold close and open for a minute or two, fell asleep for 1 hour, and when I woke up, my screen works back to normal, it wakes up when unfolded, no more waiting or hitting the power button several times. hope this stays like this.
piper_indebt said:
Oh just an update, i did some tinkering today, Good lock all updated, disabled clockface, sprayed some contact cleaner on power button, and hinges, fold close and open for a minute or two, fell asleep for 1 hour, and when I woke up, my screen works back to normal, it wakes up when unfolded, no more waiting or hitting the power button several times. hope this stays like this.
Click to expand...
Click to collapse
How to disable the clockface? what would that contact cleaner be?
thanks
firstchris said:
How to disable the clockface? what would that contact cleaner be?
thanks
Click to expand...
Click to collapse
Hi, few days now, I still have occasional blacking out, I've tried putting my phone on safe mode, and this seems to solve the problem. I suspect it may not be hardware fault, but 3rd party software, "good lock" or something else that conflicts wit one ui, that makes the flipping open lag waking up. Contact cleaner used for electrical stuff
Didnt use my z3 for about a week let the battery drain.. then charged it too 100% without turning on the phone.. my phone back to normal now.. hope it works for you guys
Hello,
I am using Z Flip 4 and last night I started having this problem as well. I can confirm 100% that my phone has no hardware nor a history of impact of any sort that's why it's really frustrating having this kind of problem.
Has anyone already found a resolution for this problem?
Z flip 4 here also. Had the same problem with the screen. Took the phone to Samsung and they changed the screen, frame and back panel's for free under warranty.
They said it's a hardware issue.
So better to take the phone to Samsung.