Android : Spontaneously Shut Down From Opening An App - Reboot Into A Frozen State
May 9, 2010
Hi, I have a pretty ordinary g1. Htc dream, unlocked (ATT is my provider). Well, I installed cyanogenmod a few weeks ago and it worked out great. I also did the 10 MB RAM hack.
Then I got greedy. I thought I'd partition the sd card and cyanogenmod would start installing apps to the sd card. This turned out to be a disaster. Probably I didn't do it right.
Everything was fine for a few days, seemed faster, etc., until I installed a new app. It was the first app installation since partitioning. Suddenly, there were problems with ALL my apps. I then thought, well uninstall app x that you just installed, but alas, I couldn't, as it wasn't listed as installed.
The phone would even spontaneously shut down from opening an app. In short, the phone became very scary and very unusable. After spontaneously shutting down, it would reboot into a frozen state, etc.
So I reformmated the sdcard, and redid cyanogenmod. I thought that this would simply undo the partitioning that I'd done, and I'd be back to where I was with a pretty good g1.
Well, cyanogenmod went okay, but there were still lots of problems. So I did a factory reset, and cyanogenmod again. This was slightly better, but it's still touch and go with my g1 now.
Home process needs force close, reddit is fun will sometimes not work. Sipdroid, even Android market, when I click it, does nothing. Sometimes when I plug the phone in with a USB cable, I mount it from the phone and it will suddenly unmount itself. Wont stay mounted.
Each of these problems will go away with rebooting, but now I've rebooted my phone maybe 30 times in the past two days. Not to mention uninstalling, reinstalling apps and rekeying in usernames and passwords, etc.
I'm writing an android application that maintains a lot of "state" data...some of it I can save in the form of onSaveInstanceState but some of it is just to complex to save in memory.
My problem is that sliding the phone open destroys/recreates the app, and I lose all my application state in the process. The same thing happens with the "back" button, but I overloaded that function on my way. Is there any way to overload the phone opening to prevent it from happening?
What possible reason could there be for you to code your apps so that they switch on in the background when the phone is turned on and use up precious battery life?
Or, why would you code your apps to stay on after I, the user, have hit the back button because I no longer want your app to run?
I mean, REALLY! Yes, I own up to being a newbie Android user, and what I don't know could fill the Library of Congress. Still, this is common sense we're talking about here. I've done some industrial app development and Enter/Exit, On/Off are basic pieces of logic in the main loop of an program in any language.
The only reason that we phone users need task killer apps is because you developers insist on creating apps that don't know when the f**k to turn themselves off.
And, it seems to me like you, the app developers, are one of the main reason why these phones have such crappy battery life. I mean, my Samsung Instinct, as bad as it was, got 18 to 24 hours of life off of one charge. With the Hero, I'm lucky if I can get 10 hours, and that's even with configuring my email download to only three times per day!
This is not hard, people. You code the app to stay off until, I, the user, manually turn it on. AND, you also code it to turn off when I, the user, hit the back button.
Yes, I understand that there are certain apps that it is advantageous to keep running in the background. So, fine, make it so those keep running. BUT, there is no possible reason for apps like Flashlight, or BBC News, or Camera, or SprintTV to have to run all the time in the background!
I am so tempted to just trash the lot of you. If I did, maybe I might not have as much functionality, but my teenager would be able to reach me late in the day because my phone battery would still have juice.
I have a compound UI component built up from a ViewGroup containing a number of TextView, ImageView etc. components. Many of these have StateListDrawables as their images/backgrounds. Is there any way of making them select from this drawable based on the state of the parent ViewGroup rather than the component itself? Ideally I want to be able to change the visual state of all children of the ViewGroup (text colour, image etc) based on the state of the ViewGroup, preferably without having to hook up complex logical code. This seems like a fairly common sort of requirement, so I was hoping it would be straightforward in Android - am I going to be disappointed?
I'm a little confused by what I'm seeing with regards to phone state transitions via the PhoneStateListener. When I receive a call, this is what happens: (call comes in) RINGING -> IDLE (I pick up) OFFHOOK (I hang up) IDLE It's that first transition from RINGING to IDLE without any interaction from me (not ending the call, not answering the call) that confuses me. Do I really have to implement an idle counter to know that an incoming call has really ended? Seems like the reported phone state represents some sort of phone state that isn't the obvious one.Is this a bug or am I just not in tune with the paradigm here?
My home screens are jumping all over the place spontaneously almost like a ghost is moving them! And then the screen locks up and I have to pull the battery. This just started yesterday out of the blue. I have not installed or uninstalled new apps this week. Pretty much cannot use phone because this.
The problem seems to happen more often since the 2.2 update. Custom ringtones for individuals, as well as default ringtone, change for no reason, as do notifications. I typically set my notification at zero volume plus vibrate, then the next day I'll hear a notification go off, and find in the settings that the checkbox for using the same volume for notifications as ringtones is checked again. So I have to uncheck it, and slide the notification volume back to zero. Is there some way to lock my settings?
Over the last few days, I've noticed my phone spontaneously restarting itself. It's happened at least 3 times since Friday, but those are the occasions it happened to be in eyeshot/earshot when it happened, so who knows how many times it's actually occurred.
I notice it also shows my up and awake time as being identical a little over 2 hours (which is how long it's been since the last random restart). It's been a bit laggier than usual, too. Not sure if either of those things are relevant or not, but thought I'd point them out.
Just starting to play around with the new X. I tried the car dock on my first trip with nav without having the charging cable plugged in. Nav seemed to stay on the turn-by-turn screen just fine, except that the screen kept timing out (as expected running on battery). Today I also plugged in a charging cable. Nav started out working fine, but then several times during my trip the X inexplicably switched away from the turn-by-turn screen to the directions screen (or to the "maps" top-down screen). I didn't see anything in the options, and can't imagine why the thing would be switching. Also, I just updated to the latest Google Maps application (last night, between the two nav tests), so maybe that had something to do with it....
Having a problem with my Screen Timeout setting. Every so often (at least once a day) the Screen Timeout setting will change so that it's not set to anything (no bubble filled) and screen will not turn off spontaneously. It, in fact, seems to turn the screen on when this happens. I find the screen on when I had physically turned it off. This is wreaking havoc with my battery life.
I have loaded two different app killers. The first one was Advanced Task Killer and the other was called Android Task Manager (I think that was the name of it), it had the little Android guy as the icon. Anyhow I liked both of them. I liked the fact that I could ignore apps and also see what was going on with memory. The issue I had was this. When I was on a call, my call screen would completely freeze up (I was still connected to the outside party) but was unable to press any keys. Even after the caller would hang up the phone was still frozen.
To get it functional again I would have to pull the battery out to reset the phone. The only time I have experienced this issue is when I have had these apps on my phone. And no I did not have them installed on the phone at the same time. I had task killer first, uninstalled it and then tried the other one. I know there is a huge debate regarding whether you need an app killer or not but I am just interested in knowing if anyone else has experienced this same issue.
left my phone on my car charger after I got home for about an hour, when I took it off it was burning hot.. looked in system app (thank you OTD) and it said my temperature was 110 degrees farenheit. I'm not familiar with the normal operation temperature so I don't know if this is off the charts or just above normal.
Ive been stalking the forums for a few weeks, reading up on all the issues and things associated with this phone and i can say ive experienced most of them (excluding rooting issues, i havent rooted).
*(of course) gps issues *phone spontaneously shuts off and battery has to be removed before it will turn back on *randomly awakes itself from sleep just to display the lock screen *painfully short battery life *no signal for a long time, have to restart phone several times before it returns.
These have all plagued me horribly the past month or so. then today it decided it wanted to....::gasp:: behave?
My battery still had half its life left when i got home tonight and its usually dead or yelping for a charge by that time (activity/usage the same today too). pages loaded quickly today and i had a signal all day.
In my XML, I've set the focusable, focusableInTouchMode, clickable, and longClickable variables to false, yet I can still click and move the SeekBar. Do I need to actually change the listener events to do this? That seems so unnecessary.
I was one of the first in Nashville to receive my phone after preordering at bestbuy. Got it Friday morning and spent all day Friday and most of Saturday playing around with it. Saturday night i was fiddling with the front facing camera to see what sort of photos it took, and i hit the shutter button and then it happened!
Literally - a flash of smoke and a spark with this unforgettable sound of cracking glass. Some sort of short has caused my main speaker (the earpiece) to completely fail, the front facing camera no longer works, and there is a diagonal crack from the Sprint logo at the top right down about 1/3 of the way down the screen on the left side.
Called Best Buy, and they're going to replace it, as soon as they get more in. Oh well. Everything else works, so i'll be using a lot of speakerphone until the replacements arrive.
For at least 5 days now the number of downloads and active installs have remained the same, surprisingly since it was changing day by day. I still see through my server that new people are registering, so definitely the counters are broken or the numbers dont get refreshed. Has anyone had a similar problem?
I've got an EVO that I have had for about a month now, and have had little to no problems at all. Yes, it has lagged a few times, but it would always force close whatever was causing the problem and restart it right away, so I had no complaints. Unfortunately, now it has frozen entirely. I am stuck on the screen with the generic unlock slider, which looks completely normal, but will not respond to touch. The slider does not move at all when I try to touch it. Sometimes, the screen will jump to the 'draw unlock pattern' screen as if the phone was simply lagging, but that screen will immediately say to try again even though I have entered no code. I have the pattern screen set up to vibrate when a node is crossed, but there is no vibrating except for randomly when I have stopped trying to draw the pattern sometimes.
I have received multiple calls while the phone is in this frozen state, and the phone will ring correctly with my custom ring tones for specific people, but will play said custom ring tone well after they have stopped calling, and remains frozen on the slider screen (I cannot answer the call). At one point, the whole screen became blurred, like the screen was covered with fog, but cleared up after several minutes.....................
I tried 2 Qik chats yesterday. The first was very smooth and successful. I was content. I called another user later that day....not so smooth. The image was choppy, but not too bad.Today, Qik was awful. Could not connect....connected but screens frozen..sound delayed.I just hope Facetime is just as bad if not.
I've had an HTC Inspire for about 8 months now, with very little problems except the occasional frustrating frozen screen or two. A few months ago, I noticed that my "volume down" button wasn't working, so I would just manually change the volume through my settings. It wasn't a big deal, just irritating.
Last night, my phone was working just fine. I even remember waking up in the middle of the night and answering my texts.
This morning, I noticed it was turned off, so I attempted to turn it on, and it wouldn't work. Thinking it was dead, I plugged it in, got the "charging" screen, and attempted to turn it on again.
I got sent to the hboot screen. Unfortunately, it is not responding to the buttons being pressed. I've never rooted my phone, so I'm pretty sure this is all due to my volume down being stuck (and therefore hard resetting when I press "power.")
Is this fixable to the extreme novice (which I'm assuming it isn't)? Or, if as an AT&T customer, will they give me a replacement, or is this beyond their realm? I know when I lost my battery cover once, they wouldn't give me a new one and said I had to go to HTC.
I installed a new Kernel on my Samsung Galaxy S plus. Its on CyanogenMod 10.1. I overclocked the default 1.4 GHz processor to 1.8 GHz. Mistakenly i set the options on the app as set on boot. Now after booting its freezing up. I can boot in Recovery mode. how to push the stock kernel file to the SD card?I don't have any backup ROMs or kernels on the phone. Neither is the Debugging mode on.I don't want to do a factory reset now. Using ADB i tried the push option
K:ADB>adb.exe push Stock_Kernel.zip /sdcard/ this also showed that the file was pushed 1877 KB/s (3665845 bytes in 1.906s) but there is no zip file on the sdcard
My phone died today, and once i put it on the charger and booted it back up it was frozen completely. I restarted the phone and still the same thing. The screen never shuts off and then drop down menu is trying to come down. I get no feedback from any touch of the screen and occasionally i will get a bunch of random vibrates back. No i do not have an ATK.
After using the unrevoked3 method to root, I downloaded rom manager and obtained the damage control rom to flash. When rom manager prompted to install, I just hit 'yes (or whatever the prompt was)' without checking backup (since I already have one) or clear the cache. Once it reboots and finishes installing, it just hangs at the 'htc EVO 4G' screen and seems to be in an infinite cycle (screen goes blank for a second then back onto the htc evo 4g screen).
when my evo is plugged into the outlet charger, the screen and the menu buttons are frozen, but the volume and power buttons work. when i unplug it from the charger, it works fine. this happened after downloading systempanel lite. this app put two icons on my evo, after uninstalling the app, one icon is gone, but the icon for the tak killer is now a wierd image that reads "problem loading gadget" does the freezing issue seem to be related to the app? what can i do to try to fix it?
So i restored my phone to a previous nandroid backup and when i went to boot my phone, its now stuck at the boot screen.... So I rebooted it back into recovery, and tried restoring a backup i know works, but same thing again. How does this happen?!? I did change the folder names that the backups were in so I didn't get confused, for example one I named one Fresh 1.1 w/ gumbo, etc. Could this corrupt the backup and if so is there anyway for me to restore the previous folder name to fix this..?
Update: Power charger had to be removed to allow update to complete.
I bought a HTC One X today and downloaded the system update. It has been in the update screen for like 40 minutes (with the green refresh icon above the phone on a black background). What's going on? Should I be worried? I've tried holding down the power button which turns it off but when I turn it back on it just goes to the system update screen again.