Related
I think I have a fairly unmodded phone...
Its still not unlocked, no rom changes, etc.
I just have programs like: PocketWeather, iLauncher and TomTom with a few simple additions like the new program that auto disconnects data after a preset time.
Well it seems very random, but when I fire off things like TOMTOM it just hangs, but not every time.
Not many. Generally speaking, when I'm having issues, it's my fault. But I do have issues with my OK button periodically disappearing, and sometimes non-responsiveness of some apps.
But, it's very rare. I usually do a soft reset every couple of days when something even remotely starts to act up.
Same with mine. I use the latest i-mate WWE ROM and find it stable.
@sk0t:
my OK button periodically disappearing
Click to expand...
Click to collapse
Do you use Magic Button?
Nope. That's what's weird about it. I'll push the OK button on the front, but the app will still be up, and the OK button will disappear on the screen. I can usually get back to the Today screen by pushing the end call button though.
mine is now very stable. There is another thread that lists the "best" things to do to stop the periodic freezing. My 2c worth is on that thread also
I use Mortsaver to lock and close the device when i'm not using it. I think this results in a very stable device. It will wake up for SMS alerts and calls but for the rest of the time it's asleep - except when you are actively using it of course.
I also use SPB Backup at 05:00 in the morning which performs a soft reset after the backup. This keeps it clean too.
Defragging the Storage card and keeping as many apps as you can off the storage card also helps.
btw I use Magic Button
I only asked about Magic Button since I've noticed that the close button disappears sometimes in "Program Manager". It comes back again with a simple tap on the window background.
See thats the odd thing.... someone else told me to try and keep my unit's memory as clear as possible to avoid possible lockups.
Is the general consensus that its the other way around?
I have the vast majority of my applications saved on my storage card, granted I have tons of space on it.
I do experience frequent annoyances when using mine.
- screen alignment sometimes acting up (will send it back, but I'm waiting for the firmware update to be released, so they can do it together)
- mediaplayer occasionally loses the storage card (solved by deleting MSMETADATA on the card)
- occasional refusal to use an existing gprs/umts (have to disconnect and reconnect)
- vpn shutting down too fast when using it with wifi (after 30s)
- activesync sometimes doesn't recognize the device, forcing me to rename it and perform a whole new sync
- occasional difficulty in connecting to the correct wifi network (e.g. when there are 4 available, it pops up a couple of times that it has a network, but the one I always connect to is the last one to be found)
...
I have been using it for about a month now (was already sent back twice for keyboard and screen issues), and had to perform 3 hard resets as the behaviour got worse. I really like the device, but I wish there were less issues.
Jörg
After seeing the specs of the Hermes, I wanted it immediately.
Last week I finally bit the bullet, sold my Wizard (Cingular 8125) and got the Hermes.
For the most part, they are the same device, with the addition of 3G and a supposedly faster processor in the Hermes.
The Wizard was about as stable as a Windows Mobile device could be, at least in my opinion. I really didn't do much outrageous with it. I had a couple of games, TomTom 6, a dialer skin, and Good Mobile Messaging installed. I'd have to reset it maybe once a week or so, sometimes less than that because TomTom would lose connection to the GPS and nothing would get it back save for a reboot.
I took my Cingular 8525 (Hermes) out of the box, and I was really impressed by the device. The keyboard is far superior even though it's only a little different. I like the styling of the Hermes better, as well as the nice gunmetal finish. Download speeds are incredible (almost 900K in my house), and setting up Good Mobile Messaging OTA only took about 5 minutes vs. 20 on the Wizard.
The only problem is the instability. Sometimes I click on the "Start" button and it will make the click noise and light up, but it doesn't drop the menu down, requiring a reset. Sometimes the phone will shut off the display and trying to turn the power back on does nothing and requires a reset. Sometimes the phone will show remnants of windows that were recently closed and that will require either opening up other programs to clear them, or a reset. Then there's the just plain ol' freeze. Not to mention that plugging in my car charger barely ever activates the charging circuit on the phone
I've had this phone for about 6 days now and I have to reboot it AT LEAST twice a day, sometimes three or four. AT LEAST. This is wholly unacceptable. If we weren't on the cusp of a firmware upgrade that is rumored to rectify most of the problems above, I'd be selling this and maybe getting a Treo 750 or a BlackJack.
I've had so many little issues like this with my Tytn, using both standard and latest roms, that I've simply decided to sell it. Its just not a great phone or a pda, although it has all the features you could ever dream of, it just never seems like its fast enough and the software just doesn't seem all that polished.
2-3 on a good day. It usully is in the range of 5-6 for different reasons. Keyboard doesn't respond, stuck on caps, no volume, random freezes, screen won't turn on. Gets annoying after a while.
i835 chirp said:
2-3 on a good day. It usully is in the range of 5-6 for different reasons. Keyboard doesn't respond, stuck on caps, no volume, random freezes, screen won't turn on. Gets annoying after a while.
Click to expand...
Click to collapse
Regarding the stuck on caps problem: if you select caps using the onscreen keyboard, then the physical keyboard is also put into caps. It is however not possible to turn this caps-lock off in using the physical keyboard. The solution is to open the onscreen keyboard, and turn it off there.
Jörg
8125 versus Hermes
I agree with you that the 8125 Wizard was more stable than the Hermes. I had one as well, and it would go weeks without resets or freezes.
You said:
" The only problem is the instability. Sometimes I click on the "Start" button and it will make the click noise and light up, but it doesn't drop the menu down, requiring a reset."
I believe this is due to the external storage becoming lost. Since WM5 doesn't expect storage to ever go away, it just freezes waiting on the storage to come back. In the case of the start menu, I think it's waiting so it can get the icons of recently used programs. Just a theory.
To fight this problem, I've loaded weather programs and the like into main memory so that external storage is only accessed when I'm playing with the phone. That's made my hermes a lot more reliable, down to a failure or freeze every few days. Not as good as the Wizard, but tolerable.
I'm having a TON of problems...
I have my Cingular 8525 HTC
ROM Version: 1.34.502.1
ROM date: 09/21/06
Radio Version: 1.16.00.00
Protocol Version: 32.53.7018.01H
I am having horrible problems with it randomly locking up, and I have to soft-reset. This usually happens when I have it on the charger overnight, and someone text messages me while it's on the charger... and of course when I soft-reset I lose all the messages! What's even worse is when it boots back up it'll vibrate, and beep for a long time like it's getting messages and I have to just ignore it and put it on silent... but there are no messages! Is there a way to fix this? What do I do?! I'm starting to get very frustrated with the phone - the only thing I use repeatedly on here is the MS ActiveSync over the air...
Do you think this could also be something to do with the variant?
I have Vario II from T-mobile, with all their stuff still on it, and I have installed/uninstalled goodness knows how much stuff, and don't really have this problem at all (touches wood). I can go for 3 or 4 days without soft reset, and then that is usually after a backup, when you have to.
I have all today screen and any software which is in startup, installed to main memory.
Also, could password screen have something to do with this? If on charge, and password protected, maybe they interfere with each other on receipt of text message. You could try removing password for overnight.
Have you tried leaving messaging running minimised overnight?
Also, have you moved any databases to storage card?
marisa4755 said:
Do you think this could also be something to do with the variant?
I have Vario II from T-mobile, with all their stuff still on it, and I have installed/uninstalled goodness knows how much stuff, and don't really have this problem at all (touches wood). I can go for 3 or 4 days without soft reset, and then that is usually after a backup, when you have to.
I have all today screen and any software which is in startup, installed to main memory.
Also, could password screen have something to do with this? If on charge, and password protected, maybe they interfere with each other on receipt of text message. You could try removing password for overnight.
Have you tried leaving messaging running minimised overnight?
Also, have you moved any databases to storage card?
Click to expand...
Click to collapse
This is an interesting idea. I will leave the messaging minimized overnight tonight. The password screen is there as a matter of policy - through my work - since the company owns the device and they push policy to it which requires a password PIN to be entered after 15min of inactivity... I'll try that?
Anyone else having that weird sound problem with it repeatedly "pretending to get messages" after a soft reboot?
i835 chirp said:
2-3 on a good day. It usully is in the range of 5-6 for different reasons. Keyboard doesn't respond, stuck on caps, no volume, random freezes, screen won't turn on. Gets annoying after a while.
Click to expand...
Click to collapse
when i have this issue i click the ok button on the side and then it startss to work again without soft-reset.
rx8volution said:
Anyone else having that weird sound problem with it repeatedly "pretending to get messages" after a soft reboot?
Click to expand...
Click to collapse
Are you sure that the sounds are messages rather than notifications?
It could be that your notifications queue is gummed up with lots of stuff. Suggest you get Memmaid or similar, download the trial and run the notifications queue duplicates remover. Then look at any of the entries marked Calendar and check to see if any of these are in the past. If they are remove them. LEAVE ALONE any notifications that are not Calendar with a description of one of your appointments or reminders.
Worth a try.
I also had some troubles. It freezes anywhere between 2 and 20 times per day. I just did a hard reset few days ago and tried to determine if any of my programs installed causes it.
It runs quiet well with nothing installed. Most freezes i get after installing SBSH WeatherMonitor.
About the sudden loss of external memory, i cannot complain. I install everything system related into the main memory. But weather and flexmail are on the card. I even take the card out having the phone running.
Not probs there.
Generally my Blue Angel is a far better phone, although bulky like my grand mother and not useful in Japan.
Thanks for the replies. After reading through this thread it seems I am not the only one with problems. Nearly every 8525 problem I've had can be solved, they just keep coming back. Like 8525 not recognizing Storage Card music. The worst for me ( happens a lot ) is that when I put the phone on the charger, then the screen shuts off to save power, but when I take the charger out the screen cannot be turned back on and needs a soft reset.
Dear all,
Had been using mini for pass 5 months, recently it experiences intermittent freezing or slow down while in the midst of doing something such as writing a text memo. If i just wait awhile it will resume back normal. If not, it will hang. Just today I have to force soft reset the phone 3 times (taking out the battery and putting it back ). It is getting annoying as it has become more and more frequent. It is as though some background program has started running and it taking up the CPU resources only releasing it moments later.
Initially I thought it was due to phone network connection seeking to connect to 3G (I disable my 3G already) so I turn on the flight mode. But the intermittent freezing is still happening.
Another reason might be that I have a lot of programs running. This I reset the phone. It became better for a while but problem recurred soon after. I have Lumos, FTouchSL, B&B tweaks running in the background.
The only thing I have not done is a hard reset which I am trying to avoid as far as possible.
Any advice?
Hi, maybe BSB Tweaks create problems!
You have to restore the original settings in BSB Tweaks and see what happens later on...
If you have to soft reset too often, you'll probably need to have the unit replaced. My first unit requires a minimum of 5 soft reset each day. (Open back cover and take out battery). Since mini doesn't have any reset button, taking out battery too often will wear out the physical unit quickly.
Note, if you ask for replacement, be sure the new back cover comes with it. Some shops will force you to replace only the core unit, and let you take back the old back cover instead of the new one that comes with the new unit.
My second unit is better. It doesn't require soft reset everyday. In fact, it can last for several days without soft reset. Soft reset becomes a rare thing.
Unfortunately, my unit hangs every few weeks. Sometimes one week. Sometimes one month. No exact duration. When it does, only hard reset can cure it. And i lose all data.
I also found out the Sense UI is a very buggy and incomplete software. It's the cause of several headaches. You can disable it. But along with it, you lose many functions, which HTC stupidly tied up to the Sense UI, and remove from core functions of WinMo. I've been forcing HTC to do something about it, thru several complaints, but unfortunately, they're just sitting on it. Maybe until enough numbers of complaints come in before they will act.
My wife has a completely stock Droid X and she always has the weirdest issues with her phone with it locking up, freezing or hanging up..
Sometimes the phone recovers, other times it needs to be rebooted manually.
Is this a known issue with this phone?? I have the HTC incredible and have no issues like this.
I havent had a problem or heard of this. Is she under warranty and get it swapped out? If not has she tried to do a wipe/factory reset? While off hold the power and menu key at the same time. A screen will come up. press the search button. Use the volume keys to scroll up and down. Go to wipe/factory reset and press the camera button.
My wife has a stock D2, and it sometimes likes to open up the voice search, or she will be typing a text message, and the g key will open the browser to google.com, or just randomly freeze up..... Maybe women have a different body chemistry that acts like a mini EMP that just destroys all electronics.... Everything electronic she has ever owned has major problems, yet mine last years........
Droid X freezing - having to battery pull.
I've been having similar issues with my Droid X. It will randomly, and often, lock up for a while, then come back to life usually. It's really annoying if your browsing the web and all the sudden the phone freezes for 20-30 seconds.
When it freezes completely, it will just freeze and the screen will remain on. I have to then pull off my protective cover and battery pull to reboot.
Battery pulls happen about once every 2-3 days. Freezes that recover are happening 5 or 6 times a day if not more.
The brief time I had the phone on stock, the issue was occuring. I ignored it and figured surely this won't happen after I root it. I'm now running latest Liberty ROM and it's still happening. Problem definately gets worse if I overclock. I'm wondering if the CPU can't even handle 1000 Mhz and needs to be underclocked just so this thing can run stable.
I'm going to test that out and see if the weird freezing and force closes go away. But it will suck loosing speed.
I unfortunately can't return my phone as I bought it used on Craigslist.
buckweet said:
My wife has a completely stock Droid X and she always has the weirdest issues with her phone with it locking up, freezing or hanging up..
Sometimes the phone recovers, other times it needs to be rebooted manually.
Is this a known issue with this phone?? I have the HTC incredible and have no issues like this.
Click to expand...
Click to collapse
Its likely due to the fact that the stock Droid x firmware sucks a load of ass. The factory blur is perhaps the biggest waste of time I've ever seen. I've had both my dinc and fascinate and x since launch day and the only remedy I've found to stop the x from doing this is flash livery. Only way to fix it at all.
Sent from my DROIDX using XDA App
Yeah man sounds like you have a bad device. If a data wipe/reset wont do it you must have a have bad device . Go back where you got it and ask for an exchange
Sent from my DROIDX using XDA App
deitiphobia said:
I've been having similar issues with my Droid X. It will randomly, and often, lock up for a while, then come back to life usually. It's really annoying if your browsing the web and all the sudden the phone freezes for 20-30 seconds.
When it freezes completely, it will just freeze and the screen will remain on. I have to then pull off my protective cover and battery pull to reboot.
Battery pulls happen about once every 2-3 days. Freezes that recover are happening 5 or 6 times a day if not more.
The brief time I had the phone on stock, the issue was occuring. I ignored it and figured surely this won't happen after I root it. I'm now running latest Liberty ROM and it's still happening. Problem definately gets worse if I overclock. I'm wondering if the CPU can't even handle 1000 Mhz and needs to be underclocked just so this thing can run stable.
I'm going to test that out and see if the weird freezing and force closes go away. But it will suck loosing speed.
I unfortunately can't return my phone as I bought it used on Craigslist.
Click to expand...
Click to collapse
Before reading all of this....note that this is just me providing a POTENTIAL explanation of why some people's phones seem to reboot more than others... this is not a generalization for all... It may not apply to you...
I think that random reboots (especially often) are related to potentially bad hardware, not being on the 2.3.34 OTA update...or user error (don't get mad, please let me explain this part!). I found that after moving off of 2.3.15 OTA that my phone was much more stable.
I notice from back when I first had my Droid X that I went crazy loading up lots of apps, and throwing widgets all over my home screens... I had custom themes flashed and lots of other stuff. While yes, blur does suck up more system resources than custom ROM's without it... you can run a phone with Blur without constant reboots.
The more apps that you have on the phone (even if not running) eat up resources. Along with that, the more widgets or notifications you have on your homescreens, the more resources that the phone is chewing through... With that said, you can SEEM to not be running anything on the phone, but the widgets in the background process' can be using up precious memory that cause the phone to lag or reboot.
Like I said at the beginning, if you don't have a lot of extra widgets and programs loaded, then yes, I would say that really sucks that your phone reboots. Moto's way of handling a resource issue (in most cases RAM)... is to reboot the phone to clear memory.
If you happen to have a lot loaded on your phone...try not to use a lot of widgets, and cut back on some un-needed apps... See if the phone reboots as often. Again, this is not me blaming anyone for their phone rebooting, simply my understanding of technology from personal experience.
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
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Yeah I think they call it the sleep of death. Happened to my recently updated wifi (8013)note also.
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
samir_a said:
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
Click to expand...
Click to collapse
I started the thread so we can see if it's happening to multiple units and what models and firmare seem to be affected. If more report the same issue, maybe this thread can be stickied. From what I read when looking for solutions, it seems to occur after firmware updates and has occurred on many of Samsung's tablets.
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
BarryH_GEG said:
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
Click to expand...
Click to collapse
On my GN 8013, I had to keep a finger on my screen while holding down the power button; that brought up the battery icon screen and from there I could reboot. Holding down the power button alone did not reboot and triggered my panic that drove me to a Google search and a solution to enable rebooting. This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
mke1973 said:
This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
Click to expand...
Click to collapse
I kind of look at it as the equivalent of the "blue screen of death" in Windows. My desktop PC throws a shoe every once in a while and it's usually tied to either graphics or memory conflicts based on the dump message. I'm guessing what we're experiencing is the Android version. As a pure guess I'd say it's something to do with memory reads/writes/buffers caused by either a management issue with the OS or an app (or combination of apps) doing something it shouldn't at an inappropriate time. And after playing with the power button I've gotten what you did (the giant battery icon showing up) and other times the Samsung boot logo. And I've had it happen twice in a week and other times once in six months; all without changing anything with the OS or apps. It's just one of life's little mysteries.
P.S. - My N2's done it but it behaves differently. It shows up a spontaneous reboot.
I had same issue frequently since last upgrade to 4.1.2 . I thought the problem is from Mobile VOIP. So I un installed it.
But today, another freeze happened. Ok, today just once. But, what's the problem?
N.b I recover it just by holding power button for 8 seconds.
Sent from my GT-I9100 using Tapatalk 2
mohammedsarhan said:
I had same issue frequently since last upgrade to 4.1.2
Click to expand...
Click to collapse
If it's happening frequently it may be something other than the random event some of us are talking about. A lot of you that upgraded from ICS to JB with all your apps intact could be having compatibility issues as not all apps have been updated/optimized yet. Older apps that are a little less mainstream and/or popular would be a good place to start to troubleshoot. Unless there's something specific to U.S. JB a lot of us have been on it since October and there haven't been any reports of frequent freezes or reboots. That is outside the random one discussed above that's not specific to JB.
mke1973 said:
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Click to expand...
Click to collapse
Pretty much exact same thing happened to me last night, for the first time ever. Took me about 30 seconds to get any response, by holding down the power button for a LONG time. Rebooted, saw the battery was below 20%, which was also odd since I had charged it overnight and had consistently been getting 2-3 days on a charge.
If it happens again, I'll go with Barry's suggestion and try a clean install, then adding apps one by one. Little disappointing though, as I've had no real problems at all with the GNote until this JB update.
Thanks,
JC
Sleep of Death...
I have the 16gb wifi GT8013 model and I am having the sleep issue too. Mine isn't "deathly" that requires the finger on the screen while powering up, or standing on your head and spinning three times while chanting "sleep of death" or any craziness like that, but every once and a while, for no rhyme or reason, I have to start it from a cold boot when I attempt to wake it with the power button. I press and hold the power button for 3-4 seconds and here comes the Samsung boot logo. Once it gets booted and connects to the wifi, I am good to go.
This happens so intermittently, with it not doing it for a couple days, or it might be within the next hour. I think I have narrowed it down to the wifi radio. Reason being...I have done a factory reset and tried running it naked and it still happened. But I have noticed the issue seems to happen when I have left the house and it drops the home wifi and then negotiates a new connection with my SIII hotspot, which I turn on before leaving the house for work, or anything that I will need connectivity for the tablet while away from the house. I don't know if it is due to roaming outside the home wife and dropping the connection, or if it is the combination of dropping the home wifi and then locking into the phone hotspot. I am so busy that I haven't been able to get that far in my troubleshooting. However, I am leaning to just the fact of it leaving a wifi signal and, I guess, it doesn't want to and gets jumbled and kills itself all together. I say that because it has happened when I have forgotten to turn on the hotspot until I got to work and then I open the tablet and its dead.
This has been happening from day one, when I bought the tablet towards the end of January. Unfortunately the Samsung warranty absolutely sucks, due to them wanting me to ship it in and do without it for 3wks and then to boil my blood even more, they want to give me a refurb unit if they can't fix this one. To make matters worse, its been almost a week now and they can't even get the shipping arrangements made yet! Needless to say, with this thing only being barely two months old, I am a little on edge with Samsung and I would love to figure it out and fix it myself. If it were something I knew, without a doubt, would be fixed with rooting and dropping CM on there, then I would. But I see there are still stability issues with most custom ROMs and I really would like to keep the functionality of the S-pen.
I have attempted to pull a log file with aLogCat and they are blank. It appears that the log files disappear when rebooted, which does me no good in figuring out what shut it down, if I can't recall the log from pre-shutdown. I have also tried aLogrec in hopes of accomplishing this, however, something isn't right because I left it recording for hours and days and the log file was only 1kb. Although, it doesn't much matter since the log recorder running in the background keeps it from sleeping to the point of shutdown, so I am assuming it is a sleep issue, due to that discovery.
If anyone has any thoughts that might help me, I am definitely all ears! This tablet is for work and school so it is next to impossible for me to do without it for 3wks...provided Samsung can get their crap in gear enough to even arrange the shipping for the service request. And I sure as hell don't want a refurb!!
Later,
Roger
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
mke1973 said:
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
Click to expand...
Click to collapse
Unfortunately, I have come to the conclusion it isn't an app issue. I have never used any VOIP service, of any kind, and I have done a factory reset and it happened before I installed any apps. Unless, of course, it is an app or service that is included in the Touchwiz junk and/or bloatware that comes with it. It happened on ICS, which is what came on it, and it happens after being update to JB. However, I only had it on ICS for a couple days and I would like to go back to it for further troubleshooting, but since it has been updated to JB, that isn't possible without rooting and I haven't decided if I want to do that yet.
--Roger
After further observation, it appears my sleep-of-death issues arise when I leave the comforts of my home Wifi. When doing so, apparently losing the Wifi signal causes the tablet to shut down completely... When asleep. If I have LogCatRec running, that keeps the tablet from falling into hibernate and the issue never happens, thus resulting in nothing interesting being logged, aside from the typical tablet activity.
Now the question arises, is it my home Wifi, or just leaving a Wifi range in general? I cannot get it to recreate the issue by simply turning off the Wifi signal it is currently connected to. However, I am now on a new Netgear router, due to the Belkin shooting craps on me, and it happened then, on the Belkin, and it happens now, on the Netgear. So, my presumption is that it has to drop a Wifi connection due to signal degredation, versus simply cutting a decent signal off at the source.
Has anyone else gotten this far with their sleep of death issue? Or is there another thread, that I've missed that I am just repeating? I am curious to see what's out there, before I send this thing off and its gone for three weeks!
-Roger
Sent from my GT-N8013 using xda app-developers app
I have no issues any longer after finding the offending app on my note and uninstalling it. I don't think there's one cause for this issue. Most often, Android OS updates seem to create program instability in some apps that then trigger the sleep of death. It gets hard to track down issues for individuals experiencing the sleep of death on their devices because we all have different apps installed. You might look at apps on your note that require WIFI to sync and are allowed to sync periodically since one of those may be the culprit. Check comments on Google Play to see if any are known to be buggy under JB. Good luck.
Mke1973, with all due respect, I dont think you are reading my post thoroughly.
As I have already said, this is not an app issue. I have done a reset and the issue still happens when I run it without any apps downloaded and installed. Unless it is an issue with a Samsung app that is preloaded, in which case the fix is still out of my hands, since the owner of the tablet can't uninstall crapware at their will, without rooting it.
Sent from my GT-N8013 using xda app-developers app
Actually, I wasn't ignoring your facts it's just that there are 3rd party apps installed by default that, if you decide to use them, require sync. Specifically I'm thinking of Evernote. Once device makers began pushing out upgrades to JB, some Android users began reporting incidents of the sleep of death when using or after closing Evernote in various Android forums. It wasn't a majority of people, but more than a smattering, but that is standard with the sleep of death. Again good luck on your hunt.