Related
Just today I have started experiencing a problem:
If I am in a program and need to open the keyboard to type something it will switch to landscape mode and then almost immediately the unit switches to the today screen. Closing the keyboard and reopening the program in question brings me back to the screen I was trying to type in, but then it goes back to the today screen. The active program will not stay on the screen long enough to do anything.
If, while in portrait mode, I use my task switcher to reopen the program I can get it to stay open. But once I open the keyboard again it immediately goes to the today screen. It will then do this for every program I open. Once open for a second or 2 it goes to the today screen. A soft reset does not help. Powering down and restarting from the power button clears it up and I can open programs and use them. But as soon as I open the keyboard again it does the above!!
Any ideas? I have not recently installed any new programs. And like I said this Just started today. I can't use the phone like this. I am loathing a hard reset because I have the unit set up the way I need for day to day work and it will take me about 3 hours to set it back up (since stupid MS removed the built in, free, back up program!)
So I need help. Thanks in advance
Narrowed it down a bit more
It seems to happen when ever the keyboard is slid, open or closed.
If in portrait and opening keyboard it will go to today screen. If in landscape and closing keyboard it will go to today screen.
Now, when it goes to the today screen if I then re-open the software with the icon on the today screen the program remains active and I can do what I need. But as soon as the keyboard moves it goes back to the today screen...
So from the lack or responses do I assume that no one else has experienced this problem? Is this a new one?
I searched the forum and found no other reference to it.....
Anybody?
Lack of responses?!? You only waited 1 hour and 42 minutes since you posted the question! It's customary to wait at least 24 hours before you bump your own topic.
Was more like 13 hours, not 1hour and 42 minutes
I posted the question at about 11pm LAST night. I asked about responses at about 12:44 pm TODAY. That is almost 14 hours....
No it is not 24 hours. But so many other questions seem to get answers with in a few hours no matter what time of day it was posted. I saw that something like 25 people had viewed it at that point and I thought I would ask....................
I use for my phone in my business and it is frustrating to use right now (if not almost impossible) . And with the prospect of a 3 hour rebuild time after a hard reset I wanted entertain other ideas first. So I asked before 24 hours was up 'cause I gotta make a decision soon as to what course of action to take......
Hi guys,
I just got my Xperia a few days ago and I noticed that my time is always delayed!
yesterday, i didn't look at my phone for a few hours and when I did, clock was delayed by an hour! I thought I was still early for an afternoon meeting but it turned out that I was late 30 minutes!
I didn't think anything of it, I just adjusted the time, maybe i had it wrong to begin with since the phone is still new, but this morning it was late again! by 20 minutes.... so I said, there must be something wrong with it?
adjusted the clock again and took a look at it after 2 hours late again by 10minutes!!! aaah!!!
Is there any fix to this?
I did a search and the HTC diamond has the same problem...the fix for the diamond is hotfix...will this work with the Xperia as well?
Any other way to fix this problem?
Help!
Thanks!
got the sameproblem since a few days... dunno what it is.
no one knows what the problem is?
still no one?
there is a a few threads on this topic on the forum, search it
there is no fix other than try the today panel for about 5-10 mins and then go back to whichever panel you were on. not sure why but that sorts it out, until it happens again. for me it happens every 3-4 weeks
the alarm isnt affected by this, also when you click the clock it will show you the latest time, i think its a screen update problem.
let us know if the HTC fix works here.
Thanks...I did try to search but no real solution...maybe I gave the wrong search words.
Most definitive answer I got was yours and the hotfix....maybe someone else can point me to the right direction?
I also noticed this....the panel time was delayed and then the time on the upper right copied the time on the panel?
What I did was I removed the clock on the panel, now my time is only delayed by 5minutes.
I'll try your suggestion.
Thanks!
maop99 said:
What I did was I removed the clock on the panel, now my time is only delayed by 5minutes.
Click to expand...
Click to collapse
Time on my Xperia is wrong mostly 7 minutes. When i synchronize it with SynchroTime it is usually 422-423 sec delayed. After synchronization within 5-10 minutes the clock again is back the 7 minutes :-/ Also clock on the panel (any) and the tray bar (upper right corner) often show a bit different time (the tray one is delayed 1-3 minutes). Can not realize what is caused this. Any idea how to fix it?
go to \Program Files\Panels\SonyEricssonPanel\ open config1.ini or config 2 and change SummerCity to 1...
alex2006mobile said:
Time on my Xperia is wrong mostly 7 minutes. When i synchronize it with SynchroTime it is usually 422-423 sec delayed. After synchronization within 5-10 minutes the clock again is back the 7 minutes :-/ Also clock on the panel (any) and the tray bar (upper right corner) often show a bit different time (the tray one is delayed 1-3 minutes). Can not realize what is caused this. Any idea how to fix it?
Click to expand...
Click to collapse
I also had clock delays on my phone, sometime 20 minutes, sometimes 5min., sometimes 2hours...now I think its fixed.
This is what I did, I removed the clock on the panel, yes, because I was experiencing the same problem as yours....the panel has a different or later time than the one on the top bar, what happens is everytime I go to the panel top bar always adjusts to the late time on the panel...so I removed the clock on the panel.
Next, I was forced to hard reset because of a program I installed kept on stalling my phone for some reason.
Now my time (on the top bar) is always on time.
Maybe the solution was just the hard reset? but I still did not put time on my panel, I don't want that problem again!
I'm in between surgery so thought I'd post a quick question where the answer is puzzling me.
Basically, I'm in wonder if this has happened to any other soul?
Picked up my HD2 when I came out of Theatre and it simply would not switch on.
Thinking it may be the battery that had run down I connected it to a power source to charge and noticed the Orange charge indicator did not light up.
Next I took out the battery and reinserted, then pushed the power button......
Still nothing.
Thinking was it a problematic battery (although it still should have switched on when connected to a power source) I exchanged the battery for the spare I take around with me.
Still nothing.
Finally, I reinserted the first battery and once again pressed the power button.
This time it fired up and loaded without any issue.
I checked the battery level ~ that indicated 56% still remaining.
So I am in puzzlement as to what may have caused it's temporary death.
Has any other had a similar experience?
Edit 01 ~ 24 Feb 2010
It would seem that to some (myself included) there is a fix that does indeed cure the problem and that is by using the software application MemMaid.
Others have tried SKTools but MemMaid seems to operate much better at terminating the freezes.
Unfortunately MemMaid is not free and seeing as HTC will not budge from this being a 'users personal settings' that is causing the freeze our only course of action at the moment is by using MemMaid.
However, please do note..... Not everyone has benefited from using MemMaid; why that is the case could be down to some individuality ~ a different setting, installed software, routine notification, etc. etc.
In other words first try the free trial version of MemMaid and if it seems to cure the the problem then do consider investing in it.... besides all this it is a great piece of software.
You can get hold of MemMaid here.
Word of Warning.....
Ensure you set up MemMaid correctly. I spent ages with member wacky banana throwing many personal messages between the two of us like fervid lovers until finally wacky came up with a setting we could use.
Below is the settings to apply to MemMaid:-
In your programs section you should see 2 icons, one called Memmaid Quick Clean and the other is Memmaid.
Click on the Memmaid icon and a window opens.
At the top left corner it should say Quick Cleaner but this is not relevant for now.
Put a tick in the the following options (the list is scrollable):
- compact ram
- windows temp files
- temp files
- ie cache files
- ie history files
- opera cache
- dead shortcuts
- duplicate notifications
- dangling notifications
- invalid notifications
- rebuild notification queue
- recycle bin
- google maps cache
Press the CLEAN button and wait for the tool to do its job then press the close button.
Next, on the bottom right of your screen, click the Tools option. From the drop-down menu choose CLEAN SCHEDULE.
Tick the following items:
- on soft reset
- daily (here you need to scroll to the right to select the icon with the 3 dots in it to set your schedule)
- show report (optional)
- show progress (optional)
Click DONE on the bottom left corner on your screen and job's a good 'un!
Edit 02 ~ 24 Feb 2010
Member jonbaker76 came up with a few extra tips to help alleviate the problem:-
1). Install MemMaid and follow settings provided by Beards & WB
[*]2). Disable the alarm (use G-Alarm maybe)
[*]3). Turn off Facebook updates
[*]4). Turn off Weather updates
[*]5). Turn off Internet Time Sync
[*]6). Wait a while before carrying out a soft reset, your Phone may just wake up
Edit 03 ~ 25 Feb 2010
Guys,
We are starting to find a pattern building up here relating the problem with Sense.
Some users don't have problems with ROM 1.48 but others Do/Did (I used to) so we can't say v1.48 was okay.
However, it's the later ROM's which seem to have the greater of the problem which could relate to an issue with Sense.
i.e. Although evident in v1.48 it was not as strong but with either Cooked ROM's or updated ROM's the problem has been magnified.
A few Guys have now tried using their HD2 without Sense and report a stable platform.
What I am saying here is if you have the problem and you can afford not to use Sense then try running your Phone without it for a trial and see how it performs...... With enough info we can pass this on to HTC.
I had a situation where I switched the phone back on (from standby/power saving mode) only to find it was dead. To get it running again I had to perform a soft reset and, like you, I found that I had plenty of battery remaining. This happened only once in three weeks of usage and I'm not sure what caused it.
James
I had a similar issue a few days ago.
I picked the phone up and pressed the power button, but nothing happened. I did the same as you and assumed that it was flat (despite me being a charging maniac!) I plugged it in and got no charging light, so I popped out the battery and put it back in. It turned on first time then.
I wasn't really concered as it's only happened once in over 3 weeks, and I'd only recently upgraded the ROM so I was ignoring any little foibles like this.
Maybe it's a little more common than I thought?
this has happened to me twice since upgrading to the new recent rom.
Beards said:
I'm in between surgery so thought I'd post a quick question where the answer is puzzling me.
Basically, I'm in wonder if this has happened to any other soul?
Picked up my HD2 when I came out of Theatre and it simply would not switch on.
Thinking it may be the battery that had run down I connected it to a power source to charge and noticed the Orange charge indicator did not light up.
Next I took out the battery and reinserted, then pushed the power button......
Still nothing.
Thinking was it a problematic battery (although it still should have switched on when connected to a power source) I exchanged the battery for the spare I take around with me.
Still nothing.
Finally, I reinserted the first battery and once again pressed the power button.
This time it fired up and loaded without any issue.
I checked the battery level ~ that indicated 56% still remaining.
So I am in puzzlement as to what may have caused it's temporary death.
Has any other had a similar experience?
Click to expand...
Click to collapse
May be a warning from HTC for your now very famous camera thread,if I were you would be carefull LOl!!
hagba said:
May be a warning from HTC for your now very famous camera thread,if I were you would be carefull LOl!!
Click to expand...
Click to collapse
....
Big brother watching us...
Beards,
Did you have any diary appointments or alarms set on the device today that you did not immediately cancel on notification or multiple alarms set/going off? If you did then this is probably a notification queue issue locking up the phone, forcing a reboot.
This symptom was very common with the TYTN when it first came out and drove me absolutely bananas!
Long shot but let me know.
WB
No... nothing was left to tie the Phone up.
I remember checking everything before I went down to Theatre earlier this morning.
In a way I'm pleased it's not an isolated case and that others have experienced something similar (sorry Guys, I don't wish it on you ~ just a little relieved I'm not the only one).
I know HTC monitor the 'Camera Problem' topic (they've told me this directly). Maybe they have some super-duper exra-terrestial monitoring machine that can achieve the Dynamics of masspoint collections..
Yep, I too have had this issue.
Was using phone normally, left it on stand by by pressing the power key. Wanted to make a call, it did not turn on. Opened back cover to do soft reset, did not turn on, started sweating..., swore at the phone and took battery out and then replaced battery and pressed power button and what do you know, booted up like nothing happened.
Am using original shipped UK ROM. Have not upgraded.
You should check this as well (first 2 might be from the same poster):
http://forum.vodafone.co.uk/index.php?showtopic=41974
http://forum.xda-developers.com/showthread.php?t=591226&highlight=freeze
http://forum.xda-developers.com/showthread.php?t=595646&highlight=freeze
I had the same problem - it happened only 2 times for a week, but it was nasty enough (and in combination with the camera problem) to make me finally send my phone back for a refund.
Basically the symptoms were similar - I would leave the phone somewhere for more than a couple of hours only to find it somehow switched off or something. The buttons light up when clicked, but the screen remains black - only battery removal helps and after that runs like normal...
I have quite a number of calendar notifications etc. - this might be a good clue!
I have the feeling that this thread might grow as big as the camera thread. Perhaps HTC fix that with a software update as well ...
A friend of mine had this problem with his HD2 on Sunday morning. He was surfing the web with it when it froze up. When he took the battery out/in again it wouldn't turn on.
He called HTC and they came to pick up his handset on monday. I guess he'll have to wait to get it back repaired Maybe he should have tried taking it out a few more times first.
deyanp said:
You should check this as well (first 2 might be from the same poster):
http://forum.vodafone.co.uk/index.php?showtopic=41974
http://forum.xda-developers.com/showthread.php?t=591226&highlight=freeze
http://forum.xda-developers.com/showthread.php?t=595646&highlight=freeze
I had the same problem - it happened only 2 times for a week, but it was nasty enough (and in combination with the camera problem) to make me finally send my phone back for a refund.
Basically the symptoms were similar - I would leave the phone somewhere for more than a couple of hours only to find it somehow switched off or something. The buttons light up when clicked, but the screen remains black - only battery removal helps and after that runs like normal...
I have quite a number of calendar notifications etc. - this might be a good clue!
I have the feeling that this thread might grow as big as the camera thread. Perhaps HTC fix that with a software update as well ...
Click to expand...
Click to collapse
I had something similar this morning, I have been using the alarm for the last 2 weeks with no problems. this morning the screen lit up, i saw the notification on the top but there was no noise. as a veteran of WM i dismissed it as "typical". however, the screen then went blank, the buttons would light up but nothing happened. I reset the phone to no avail, button still lit up but no screen - mild panic. removed and refitted the battery and all has been well since.
won't be too chuffed if it happens again....
rivets
Beards,
Notwithstanding that this may be some kind of new software or hardware problem, I just wonder about the notification queue.
I would try using a copy of SKTools to clear the notification queue ( I think you can do other tweaks as well but it's been a while since I used it) and see what happens.
Did you have any missed calls you did not answer today (another possible culprit, linked into auto screen lock = disaster).
I am simply putting ideas out for you to try to narrow the problem down. Don't know if any of this will work.
WB
PS: Just had another thought; have you installed an application onto your SD card that is on-screen? Used to have this issue with a weather application, sat on screen but installed to the SD card.
If the phone went into sleep mode and the application polled the weather servers then it would die a horrible death. De-installing and reinstalling to phone memory solved the problem.
Again its a long shot but you never know.
WB
Ive had that same problem twice last night within th space of 1/2 hour and the today i ran fine up until about 5pm today, where it froze, I updated the rom on sunday from O2 1.43 hope this is not gonna be a problem, anyone know where to get O2 1.43 rom just in case I have to return
wacky.banana said:
Beards,
Notwithstanding that this may be some kind of new software or hardware problem, I just wonder about the notification queue.
I would try using a copy of SKTools to clear the notification queue ( I think you can do other tweaks as well but it's been a while since I used it) and see what happens.
Did you have any missed calls you did not answer today (another possible culprit, linked into auto screen lock = disaster).
I am simply putting ideas out for you to try to narrow the problem down. Don't know if any of this will work.
WB
PS: Just had another thought; have you installed an application onto your SD card that is on-screen? Used to have this issue with a weather application, sat on screen but installed to the SD card.
If the phone went into sleep mode and the application polled the weather servers then it would die a horrible death. De-installing and reinstalling to phone memory solved the problem.
Again its a long shot but you never know.
WB
Click to expand...
Click to collapse
Even though my profession is based on absolute accuracy in detail, when it comes to finding out why the HD2 died I'll try any long-shot.
There were no programs loaded though and I know nothing was paged to make the Phone send any notifications.
I'll have a good check at possible programs/dll's later though.
Thanks.
I've had the same a few times. Probably the reason was overloaded main memory. I removed some mp3 files, but the situation wasn't change.
htc touch pro2 vs hd2... just got the answer!
a day ago... i was unsure about the upgrade. i had posted tis msg in xda but was advised by a senior member tat it was worth the upgrade n i culd find all my answers to the query here. here was my msg...
"hi all. with all the hypes surrounding htc hd2... n my htc touch pro2 fast losing its crown of being the best winmo device in the market... shuld i upgrade to the hd2? n watz wif the glass screen? wuldn't it crack easily? it's glass! appreciate everyone's take on this. the only selling point tat is tempting me away frm my pro2 is abt the speed... 1ghz vs my miserable 528mhz... sad. everyone's talking abt its blazing speed. is it tat obvious?!
then again there's tat camera issue... the infamous pinkish spot, which htc support claims it's related to the 1ghz dragon fella... software related... n restricted to only a selected few?! so it's like going2 the lottery n c who gets the infected piece is it?! bottom line is... my pro2 seems like a honda civic... n the hd2 is purportedly a nissan skyline, but wif so many question marks hanging over its head, shuld i still go for the upgrade? thnx!"
guess wat, after reading most of the threads here... i think i'll stick with the htc touch pro2. the hd2 has way too many issues... even worse than the camera thingy tat i knew abt... but the number of issues tat r highlighted here abt the hd2... is enuf2 make me say no to hd2.
This thread here reminds me to some issues with WinMo 6.5/Manila 2.5 ROMs for the Xperia X1: Over there in the forum, you can find quite some postings describing the "standby of death" problem.
Just very close to some of the other issues we now face with the "real" Leo, too. In fact, there are more "similarities" like the stand-by issue, and nobody was really able to clearly reproduce the problem as there seems to be no pattern. The same problems are not existing in WinMo 6.1/Manila 2.1 ROMs for the Xperia - but some in a WinMo 6.1/Manila 2.5 version, when I follow the thread correctly.
I do strongly believe that there are, underneath the hood of Leo´s operating system, quite some nasty bugs in WinMo as well as Manila. I cannot imagine another explanation why 2 totally different devices with very different hardware (parts) would show the almost exact same issues.
Of course, porting the Leo ROM to something like Xperia may bring some issues, but most apparently, most bugs are coming from MS and HTC, not the talented chefs here. (One more reason to look forward to custom ROMs for the Leo. No good sign for HTC though, frankly spoken...)
mine die this morning too ... alarm didnt go off
but press and hold the power button wake the phone up and alarm start ringing. Then I power it off, and all the other buttons does not turn on the phone other than press and hold power button = soft reset ... weird
Camera patch is out today
waiting for new ROM release
Same thing happened to me this afternoon. The phone wouldn't start up when I pressed the power button so I tried holding the power button down to force a soft reset. At one point all the buttons lit up but nothing more happened. Eventually I pulled the battery out, stuck it back in and then the phone started.
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
roadkizzle said:
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
Click to expand...
Click to collapse
Something probably is messed up in the upgrade process.
Simple solution, flash the 2.2 sbf and you should be good.
roadkizzle, Something doesn't sound right at all with your update. I would try to remove the battery for a minute and reboot. If you still have issues I would try a factory data reset. If that doesn't cure your ills then flashing the 2.2sbf as bandroidx suggested may be in order.
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
roadkizzle said:
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
Click to expand...
Click to collapse
flashing the sbf already updated your phone to 2.2. You don't need to do anything else
I hope reflashing did the trick for you. That experience sounds nasty...
Sent from my MB520 using XDA App
Well, after a couple of hours of playing with my phone it's seeming better. I have been playing a few games of Worms, and my normal surfing the internet and so far I haven't noticed any real lag. The test will be my day through tomorrow.
I was just really confused because I was following the instructions from the Flashing SPRecovery SBF to a Motorola Droid youtube video, and his SBF file really seemed to only change the recovery screen. It looked like he still had to go through the actual update.zip process to make the actual updates to his phone.
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
roadkizzle, It sounds like you are still having issues. If you look at the system version in "about phone" in settings menu does it say version 37.4.0.MB520??
Yes, it says Version.37.4.0.MB520.ATT.en.US
roadkizzle said:
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
Click to expand...
Click to collapse
what apps do you have installed?
look in task master and get rid of any auto-ends and reboot and see if that makes a difference
Well, immediately after removing the AT&T apps from the auto-end list and rebooting, I thought I noticed some lag initially, but I've let it run for a few days now doing everything I was before and I've not been having any of those issues recently.
I'm not sure what it was. I wasn't very aggressive adding apps to my auto-end list, really just Maps and the AT&T apps. I added maps after a while because when I would use it once it would stay open and I'd notice later on that it would have been a major consumer of my battery, and I couldn't figure out how to close it fully.
Glad to hear things are going better. I had some issues totally unrelated to the apps I had in auto-end but pulling all of them off of auto-end got rid of the issues. Froyo is supposed to minimise the need for having to add apps to auto-end in task manager. Regards
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
humanque said:
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
Click to expand...
Click to collapse
Try taking things off of the auto-end list. You shouldn't need the task killer because android manages apps on its own (it's supposed to manage apps better in froyo than in 2.1)
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
kyngnothing said:
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
Click to expand...
Click to collapse
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
https://market.android.com/details?id=org.jraf.android.nolock
jorgonv said:
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
Click to expand...
Click to collapse
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
PS . If you can't get your screen to stop locking all the time with froyo 2.2.1dissable it in the same location ID # 61 screen_lock set to 0. ),
Click to expand...
Click to collapse
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
kyngnothing said:
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
Click to expand...
Click to collapse
You can always sbf if you get locked out. your data will also be kept
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.