I'm hoping I can write this off entirely as an Opera Mobile bug/glitch, because *IF* I remember correctly this only happens with Opera Mobile open. But here's the issue:
Last night I was going between Opera Mobile, texting and finally, a 2.5 hour call. Needless to say, running on ~30% battery, it died. So I plugged it in and let it charge. Over the course of the next 1-2 hours I moved the phone and the charger all over the house. I went to bed but I wanted to check a couple forums first so I fired up Opera Mobile and started browsing. Well about 15 minutes later I wanted to check something from an earlier text so I pressed the 'Home' key and... nothing. All good, I thought, because this has happened a few different times where all I had to do was press 'Home' again and it went back to the main TF3D screen. So I pressed 'Home' again. Nothing. Again, nothing. So I tried the 'End' key, still nothing. It was at this point I took the phone off the charger and noticed that the white ring was still lit up and pulsing - like it does when it's charging. It wasn't completely frozen, the touch screen was still working. So I brought up the start menu and hit 'Today'. I then slid the keyboard out and it changed orientation fine. I hit 'Messages' and it lagged up so bad that when I clicked one of the conversations the loading icon appeared but was just still. I let it take it's time and eventually made it back to the 'Home' tab of TF3D. The last thing I did was to check how much memory (RAM) was being used and what was running. Oddly enough, I had 103 but not a single program was running. The thing is, I never closed Opera Mobile and when I went over to the 'Internet' tab and tried to launch Opera Mobile from there, it showed the green "selected" background but did NOTHING.
Any ideas on this? Like I said, this has ONLY happened when using Opera Mobile (if I remember correctly). Something else I should add... Yesterday I changed a couple settings in 'Advanced Config', light sensor, End key delay and G-Sensor polling rates. Do you think that having too high or low a light sensor threshold could mess with things laying in the dark? I'm going nuts with worry this morning and I want to make sure that it's not a phone/hardware issue.
Anyone have any stab in the dark as to what this could be?? I installed those ATI drivers and didn't like them and problems they caused so I went back to the backup key I had saved. Does this help or have anything to do with my situation?
Bump.
Quick update: I've been using Opera Mobile off and on today and no problems. Could it have been battery issues plus an OM bug? Or is that technically impossible?
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.
AT&T Fuze screen issue - bottom menu-area of screen is flickering almost constantly
(Forgive me for the length of this post. I am just trying to provide as much information as possible! If anyone has encountered this same or similar issue, your help is greatly appreciated).
I need help! (professional and otherwise) ...with my AT&T Fuze (rebranded Touch Pro).
I am developing a game for Windows Mobile called Scrobble (http://forum.xda-developers.com/showthread.php?p=3206316&posted=1), and I left it running overnight.
My screen is set to turn off after 1 minute, and my device set to sleep after 5 minutes when plugged in to external power.
I had the Fuze plugged into wall outlet power to recharge. I left it lying, like I always do, face down on a black soft-leather CD case (so the glowing charging light doesn't bother me).
I left it alone for the 7.5 or so hours I was asleep. When I woke up in the morning and picked it up, the screen was on. It usually is not on, and I don't think I pressed the button to activate the screen.
When I looked at the screen, the Scrobble program was still running, and the bottom menu portion of the screen was flickering. Scrobble has two menu buttons at the bottom -- "Turn" and "Game" -- with a SIP keyboard icon in between them (same as nearly all WM apps).
In any other program, or the Today screen, the menu portion of the screen flickers (the brightness constantly and rapidly fluctuates consistently... like a fluorescent light that is on its last leg).
I did a full power off and power on, and during the "world phone" screen and the the AT&T 3G "power up" animation, the flicker was -not- there. But as soon the Windows Mobile loading/splash screen appeared, the flicker returned, in the exact same spot.
And I can see the ghost "Turn -- [SIP] -- Game" menu in the flicker. But I don't think it's burnt into the display, because it's not there during the first two loading/splash screens.
Currently I have the battery completely removed from the device and will leave it out for a while. If that doesn't work I will do a hard reset.
Any help would be greatly appreciated!! (This device is about 2 months old -- does HTC provide any support for it directly?).
Fixed
Phew! My screen flicker issue is no more.
I'm not sure if it's because I took the battery out and let it sit and think about what it had done for ~22 hours, or if it's because it just went away after a while (with the battery out for 22hrs). But either way, my Fuze is back to normal!
So if anyone leaves theirs on overnight and wakes up in the morning to a flickering ghost of a menu at the bottom, my suggestion is to fully reboot it, then take the battery out and leave it out overnight!
(It's kind of nice going a full day without any phone calls!!).
good for you.. you dont need a new phone giving you damage issues already... glad to hear that its gone
Thanks you for this post. I am going through the same thing with my ATT Fuze. This time it is Tomtom that I left running overnight with the screen turning on and off. I can add that the flicker and ghost is there the second the phone powers on. I have already hard reset and took the battery out for a few mins, but the flickering still there. Now I will take the battery out for several hours and hopefully it will be normal again.
I had a similar issue this week. I was using the phone all day, getting emails and phone calls, no problems. I get home and go to charge my phone and it doesn't appear to be charging. I flip on the screen and the whole screen is flickering on and off like it's not getting enough power. I charged the device over night, hard reset, pulled battery for 24 hours and still it won't go away. I just got the device thru amazon so I already reordered a replacement.
I've never left my screen on for hours at a time and I sometimes run into that same issue. The bottom of the screen flickers, and I can see a ghost image of my left and right soft keys when doing things that pull up a dark grey or black screen, like adjusting the volume. I usually try a few soft resets, and if that doesn't work I turn it off and take the battery out for a while. From what I am reading it seems to be correlated with extended periods of screen usage, but my screen has rarely been kept on for more than 30 minutes at a time.
Not to beat a dead horse or anything, but I was just having the same problem with my Fuze: the bottom quarter of the screen was flickering, but without the ghosting you spoke of. Out of curiosity, I went into my "Power Settings" menu, and for some reason the "auto adjust backlight" was unchecked, and the brightness settings were maxed out. I checked "auto adjust backlight" and the flickering stopped. Not sure why, but thought I'd add it to the thread.
kart_racer3 said:
Not to beat a dead horse or anything, but I was just having the same problem with my Fuze: the bottom quarter of the screen was flickering, but without the ghosting you spoke of. Out of curiosity, I went into my "Power Settings" menu, and for some reason the "auto adjust backlight" was unchecked, and the brightness settings were maxed out. I checked "auto adjust backlight" and the flickering stopped. Not sure why, but thought I'd add it to the thread.
Click to expand...
Click to collapse
Yeah I did notice that it's only really noticeable when the screen is set to max brightness. Setting it on auto adjust cleared it up for me also.
proj3ktpat said:
Yeah I did notice that it's only really noticeable when the screen is set to max brightness. Setting it on auto adjust cleared it up for me also.
Click to expand...
Click to collapse
thx guys...helped me out too...
Just sent my unit in for repair (under warrenty) due to the screen flicker issue, lets see what happens when it comes back.
I just started to experience the flicker today. Has be somewhat concerned. The device is only two weeks old.
However, it seems to have stopped by itself while I was searching the forums for an answer. If it returns, I'll try the 'remove battery' method and see if that helps.
Also, I love Scrobble! Shame it doesn't work on QVGA displays. Or, at least, didn't on my Wizard...
Related thread
Hey guys there's a thread with the same exact issue and a screenshot on the first post.
http://forum.xda-developers.com/showthread.php?t=535099
Seems to be something related to the Hardware 3D Acceleration driver for Windows Mobile, I get this problem only once 3d has been activated.
If Sense/TF3D is turned off, I never see this problem. It only comes up once a game or Sense has been launched.
I can also boot into Android without 3D activated and not have this problem, but if I run Sense then go into Android I get the flicker from a Windows Mobile screen while in Android.
protwitness: That doesn't seem to be the case (for me, at least.) I don't run TF3D and it still happens. I can't really discern what the trigger is, but I have a feeling it has something to do with the screen brightness auto adjustment. (Sometimes, I'll turn my phone on when it's dark and it jumps to full day-light brightness for some reason.)
I've adjusted to it and it doesn't really bother me any more.
Hi guys,
When I get a message the phone vibrates 3 times, like normal. But sometimes randomly it vibrates 1 time and then unlimited vibration. Until I get it out of my pocket and press the powerbutton so the screen goes on again. When the screen is on again the phone resumes the 2 vibrates. Very strange. I had it on multiple roms with different radio's. I don't use TF3D but HTC Home Plugin VGA edition.
I've experienced the same issue you speak of with the stock ROM, and I haven't found a solution or cause yet either.
I think it was this what caused my phone to sometimes go out. Because the vibration consumed all the power.
Do you use Touch Flo?
_MsG_ said:
Hi guys,
When I get a message the phone vibrates 3 times, like normal. But sometimes randomly it vibrates 1 time and then unlimited vibration. Until I get it out of my pocket and press the powerbutton so the screen goes on again. When the screen is on again the phone resumes the 2 vibrates. Very strange. I had it on multiple roms with different radio's. I don't use TF3D but HTC Home Plugin VGA edition.
Click to expand...
Click to collapse
That would be the angry bee. It is something that just happens. I've had it so bad that I have had to soft reset the phone. It only happens to me every great once in a while. However, I haven't run the stock rom since about 2 hours after buying the phone.
has happened to me twice now.
ive had the phone about 2 months.
Dane Austin said:
That would be the angry bee. It is something that just happens. I've had it so bad that I have had to soft reset the phone. It only happens to me every great once in a while. However, I haven't run the stock rom since about 2 hours after buying the phone.
Click to expand...
Click to collapse
I've had it happen to me a few times and had to soft reset it to make it stop. It doesn't happen too often, so I haven't been too worried about it.
I've had it happen when I launch an application just as it is starting to vibrate to signal a notification.
Do you guys also always have it as the second vibration? When it hangs it always is the second vibration at me. And when I press the screen again he makes 2 after it again.
I had a similar issue with the initial stock rom - my wife messaged me in the middle of a meeting and my phone would not STOP VIBRATING. Since it was on the desk, it buzzbuzzbuzzed really loud.
Now I'm on the Energy 3.0 rom and have not had an issue. Even with the updated leaked stock rom I didn't have the issue.
I discover that it only vibrates wrongly when I have the screen off. Pretty annoying though.
Don't we use some kind of stuff in common?
I use:
HTC Home VGA Edition for front end instead of manilla
HomeScreen++ for the handy shortcuts
I checked some things again, I am not 100% sure but I think it was HomeScreen++ that caused the problems here. The exact settings: at the Tools tab "Lock if Display is Off and vice versa, which didn't work anyway at the touch pro (did work on htc's I had before though), but I checked it off and now it still rings 3 times and no less or more. Hope this was it.
I do not use HomeScreen++ and it happens to me at least once a day, sometimes twice. Mine always seems to happen on the third vibrate, it will do the first two and then the third one just stays on. I press the power button for the screen to come back on and it stops.
I have it too sometimes.
EnergyRom 3.0
And you guys have something that auto lock the screen when you press the power off button? Or do you lock the screen before pressing the power button? Because here it seems to have something to do with the locking in combination of the standby mode (screen off)
Hey,
So after having browbeating my phone for 1½ years (and recently started bragging about it) something major has finally happened. Shouldn't have jinxed it.
Basically, it pushes buttons in random order. The things that happen (and can start to happen all the time, even before I enter my PIN):
Volume going up
Volume going down
Connection manager opens
Camera turns on
Switches between modes while in camera (panorama, burst etc)
I'm unable to try out if I can access connection manager and camera through volume up/down, but if that's possible then I'd say it's a problem with the volume up and down buttons on the side.
Also: I've lost all connection what so ever with my operator.
I recently flashed to Energy Phoenix 2.0 feb 26th build - Sense 2.1 21892 and it worked as normal for 1½ week. Then today I received a text, and then I lost signal and all the button mashing started happening.
It drains 50% of the battery in about 2hrs, leaving me think that it's doing something even with screen off laying on my desk.
Just now I flashed to Energy Leo feb 26th build, 21892 Sense 2.5 version and it's still all weird.
Anyone know what's going on?
UPDATE: argh, clicked the wrong button and lots of text disappeared
anyway. shortly: the buttons stopped working altogether for a short while, and it stopped ****ing around. Then they started working again and the ****ing around resumed. At one point I couldn't navigate away from the volume screen because of horrendously fast changes in volume. I've tried hard-resetting, but it wants to start up the camera the moment i'm done calibrating my pen resulting in canceled "first-time-installations-scheduled-after-hard-resets", with angry red letters.
stoopid phone
I Had the same problema, but worse, i have the same problem with the keys but also now the led of the flash of camera still on
So the ligh is always on, also when the device is off, i dont know what to do because im in mexico and no many people know abaut repair this phone.
I hope anyone can help thankss