This has been an ongoing problem with my G1, related to modded ROMs from what I can tell.
I suppose I should point out, before going into my problems, that I am indeed a noob.
So, back to when I first got my G1.
Quite quickly, I decide I want to root my phone. I follow Cyanogen's guide through every step, and I am able to boot. Cyanogenmod works fine for about a couple weeks.
Suddenly, while I'm listening to music and on the home screen, the screen seems to tear, I suppose you could call it. I don't know the real term for it; it's a problem that usually occurs when programs use indirect allocation of memory. This causes my screen to freeze. When I hit the power button, followed by the menu button (to turn off and on the screen) the backlight turns on, but there is no display. Restarting does nothing, no G1 screen and no recovery.
Just pulling the battery for a brief amount of time seemed to fix it. This quickly stopped working, forcing me to flash ROMs until I had enough of a screen to go back to scratch. It used to only happen when multitasking on the home screen, but with a modded rom, this has started to occur even on boot. Eventually I had to go back to using unrooted OTAs.
I've had this happen with TheOriginal AOSP 1.6, Cyanogenmod 4.2.14.1, and Super-D 1.9.2. I've tried both Amon's and Cyanogen's recovery images, with and without the Danger SPL. Actually, the Danger SPL would stop the screen after a shutdown.
Does anyone have any idea what's going on or if I can run modded roms on my phone?
Tony_SpaZ said:
This has been an ongoing problem with my G1, related to modded ROMs from what I can tell.
I suppose I should point out, before going into my problems, that I am indeed a noob.
So, back to when I first got my G1.
Quite quickly, I decide I want to root my phone. I follow Cyanogen's guide through every step, and I am able to boot. Cyanogenmod works fine for about a couple weeks.
Suddenly, while I'm listening to music and on the home screen, the screen seems to tear, I suppose you could call it. I don't know the real term for it; it's a problem that usually occurs when programs use indirect allocation of memory. This causes my screen to freeze. When I hit the power button, followed by the menu button (to turn off and on the screen) the backlight turns on, but there is no display. Restarting does nothing, no G1 screen and no recovery.
Just pulling the battery for a brief amount of time seemed to fix it. This quickly stopped working, forcing me to flash ROMs until I had enough of a screen to go back to scratch. It used to only happen when multitasking on the home screen, but with a modded rom, this has started to occur even on boot. Eventually I had to go back to using unrooted OTAs.
I've had this happen with TheOriginal AOSP 1.6, Cyanogenmod 4.2.14.1, and Super-D 1.9.2. I've tried both Amon's and Cyanogen's recovery images, with and without the Danger SPL. Actually, the Danger SPL would stop the screen after a shutdown.
Does anyone have any idea what's going on or if I can run modded roms on my phone?
Click to expand...
Click to collapse
Please post what you have on your SD card, partitions, sizes, like that. Make your self a signature with all that stuff and you'll only have to do it once.
Also include if you are running swap compcache or whatnot. I know some of the roms you tried do some of those by default.
I'm still using the 1gb that comes with the phone with one FAT32 partition, should be getting a 8gb class 6 tomorrow. I had tried using a 256mb ext3 and a 64mb swap, but reformatted in case that was the problem.
Tony_SpaZ said:
I'm still using the 1gb that comes with the phone with one FAT32 partition, should be getting a 8gb class 6 tomorrow. I had tried using a 256mb ext3 and a 64mb swap, but reformatted in case that was the problem.
Click to expand...
Click to collapse
I have to admit, I was thinking the same thing. I have never tried one of the modded roms without the ext partition but it should run fine. Usually slow downs that occur over time are cache (swap) related.
I would get your new card, partition it using amon-ra, wipe everything, and use the newest super D.
If it still fails, you may want to look for a stock version. There should be one here somewhere with only root added.
Alright, just got the new card. Should be done with all installing within a few hours. Fingers crossed, eh?
<crosses fingers> lol
Hmm, phone is acting even weirder than before. As of right now, I get my screen back every reboot, but with a custom rom, it fails on boot. The boot screen will freeze, followed by a backlit black screen. I'll keep trying, but I thought I'd see if anyone had any helpful tips, perchance?
(This is attempting to get Super-D going, although I had tried Cyanogenmod earlier with the same result. Downgrading with the dreaimg.nbh still boots fine, however.)
E: Although I'm not sure what exactly did it, it seems to be working now... for now. The fact that the glitch was similar but still improved gives me hope, however.
Crap, it died again on me using Cyanogenmod with Enoch, both fully updated. Anyone know where one of those stock with root roms are?
E: Actually, better yet, anyone know if there's any way I can tell what I'm doing with my black screen? I'm trying to apply stuff with RA-dream, but it's kinda hard, what with the lack of vision and what-not.
Tony_SpaZ said:
Crap, it died again on me using Cyanogenmod with Enoch, both fully updated. Anyone know where one of those stock with root roms are?
E: Actually, better yet, anyone know if there's any way I can tell what I'm doing with my black screen? I'm trying to apply stuff with RA-dream, but it's kinda hard, what with the lack of vision and what-not.
Click to expand...
Click to collapse
you can do a logcat right before it goes out connect your phone to your comp and do adb logcat and do everything your normally would do and if it goes out again and you see a significant in the log from the phone dying then copy that text and post it here. maybe someone can help out.
Ah, I may have explained badly. I've no display at all; no G1 logo, recovery console, or spl. They still work, though. Alt + T while in the recovery console still throws it into USB mode.
If you install the android sdk on your PC, you can use the USB lead to log all activity on your phone.
You would then see where it is crashing (and with any luck why)
It would be painfull because it seems random and intermittant, but atleast you would know why and have a point to look at.
http://developer.android.com/sdk/index.html
btw, original rom (rooted)
http://forum.xda-developers.com/showthread.php?t=538456
Sadly, it locked up yet again. It seems this is the logcat entry linked to the problem;
W/SurfaceComposerClient( 1297): lock_layer timed out (is the CPU pegged?) layer=0, lcblk=0x
42664020, state=00000042 (was 00000042)
W/SurfaceComposerClient( 101): lock_layer timed out (is the CPU pegged?) layer=3, lcblk=0x
426301a0, state=00000007 (was 00000007)
This is looped until the power button is hit, which then keeps anything from appearing on the screen.
Ah, now I can't boot. It seems my GPU is acting up in some way shape or form.
I/SurfaceFlinger( 110): SurfaceFlinger is starting
I/SurfaceFlinger( 110): SurfaceFlinger's main thread ready to run. Initializing graphics H
/W...
D/SurfaceFlinger( 110): pid 110 requesting gpu core (owner = -1)
W/SurfaceFlinger( 110): couldn't grant gpu core to pid 110
D/EGL ( 110): requestGPU returned -1
E/libEGL ( 110): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
Shortly followed by...
E/libEGL ( 110): validate_display_surface:536 error 300d (EGL_BAD_SURFACE)
E/libEGL ( 110): call to OpenGL ES API with no current context
I/SurfaceFlinger( 110): OpenGL informations:
E/libEGL ( 110): call to OpenGL ES API with no current context
Which then throws it into a loop.
I would install the latest Cyanogen and make sure the phone is clean.
Run a logcat from boot, and then when it crashes post the full logcat + info on the bugs cyanogen page.
http://code.google.com/p/cyanogenmod/issues/list
The support seems to be good there, but they will want a clean install etc..
Related
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy
IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.
The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S
well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.
just leave it off for a while and keep it someplace dry and warm so it can dry out.
You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup
Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.
I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.
Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x
I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??
This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...
same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!
Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol
I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.
I wonder if any of you have tried restoring your latest back up?
Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.
Hi guys, I have had a G1 for over a year now, and it has been rooted for that long. I began using cyanogen's mods since 4.1 or so, and they have been rock solid until recently, when I upgraded from 4.2.6 to 4.2.7. Ever since that upgrade, my phone has been "freezing" and rebooting at seemingly random intervals.
First, let me try to define what I mean by freezing: this usually occurs when the phone is put to sleep, and it just refuses to wake up. The screen remains black, however my notification LEDs continue to flash (if they were flashing before). Sometimes, the phone freezes while I am using it; buttons stop responding, and opening/closing the keyboard does not change orientation. The phone usually gradually slows down to a crawl before this type of display-on freeze happens. In both cases, I am able to restart the phone by pressing call+end+menu buttons.
For the restarts: these started happening recently, I'll guess after 4.2.9. This always happen while I am using the phone. It'll pause for a second, like it's frozen, then restart back to the G1 boot screen a few seconds later.
I have tried wiping, repartitioning my SD card from scratch, using the phone without any of my apps installed, etc. The only thing that seems to fix this is if I downgrade back to 4.2.6. I have tried to narrow this down to the best of my ability, but I still cannot figure out the cause. My question is, how can I begin to troubleshoot this? Is there a log or some way for me to see what is the last thing the phone tried to do before it froze/rebooted? Right now, I don't even know where to begin.
well for the phone freezing it MIGHT be too many apps running in the background and eating up CPU usage...download advanced task killer from the market, it allows you to close apps that run in the background.
as for the random reboots, i am almost certain it has to do with the rom you are on. there should be an app called "log collecter" in your app tray, it comes with the rom, try and get the logcat from it when your phone reboots, and send that logcat to cyanogen via the link he provides on his thread.
2 things that I can think about:
1. Wipe you dalvik-cache
if that does not fix it
2. This may be a good time to re-format the ext 2/3/4 partition of your card and do a complete wipe.
I have this exact problem, it first started with random sd card errors "removed sd card" with an sd card inserted, and now the black screen of death, I reformatted and repartitioned my 8gb transcend class 6 card and flashed latest cyanogen. Today I got the black screen again so I used nandroid and went back to cyan 4.0.4, I still got the black screen freeze running old rom but so far sd card is working so not sure what the cause is, bad sd card? I just got this card a month ago... or phone going bad?
yeah, i get the freeze, its usually when i am running multiple resource eating apps. Try advanced task killer for a convenient notification bar click away from closing apps.
I also get the other problem where it wont wake up! Seems like we are running into the same problems under the same ROM. When it doesnt wake up i usually wait a few seconds and try pressing other buttons than the menu button to wake it up when its not turning on. A combination of waiting 5 seconds and trying a different button usually wakes it up.
Hey guys, thanks for the logcat info.
The most frustrating part about this problem is that it is unpredictable; it just happens when it feel like it and is impossible for me to reproduce, therefore I cannot figure out the cause nor can I tell whether or not any changes I make have any effect.
I do have ATK, and I use it regularly. It still doesn't stop this from happening. In fact, I installed ATK in order to try to solve this, which means before this started occuring, I did not even have ATK installed nor did I have this problem.
Can anyone tell if there were any significant changes from cyanogens 4.2.6 to 4.2.7? I see the changelogs, but most of it doesn't really mean anything to me because I don't understand what its talking about.
Yeah I usually get the freeze after installing a new rom onto my htc dream 32a. I just take out the battery and put it back in. Then I reboot and have no problems after that.
try going back to previous rom you had and see if the problem still exists... could possibly be an issue with latest update for rom...
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Sound's like Kernel panic. Wipe everything and install soemthing stable like cyanogens 4.2.15.1 or dwangs rom. Didn't know there was anything worng with SuperD's kernel though.
jaekim708 said:
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Click to expand...
Click to collapse
Since the rom relies on apps to sd I would guess the ext is borked and maybe the fat32 as well. I would reformat the whole thing to fat 32 then reformat to ext2 or 3. Load Dwangs rom for testing (easier to get running just as a test).
So I wiped my SD (ext4, dalvik, fat32) and tried cyanogen. Then I tried Pays. Reboot problem's gone, but neither of them is reading my SD card.
I'm assuming its just a matter of backing up the SD and repartitioning? I'll try that next when I have time.
Thanks for the help guys! Lastly, any ideas on why this happened? It'd be hard to pinpoint the exact reason, but I'm assuming I'm not the only one who had this problem - how did other people get to the situation I'm in?
I wiped all of my SD, repartitioned, wiped the phone, flashed AOSP 1.6. w/ root and "expansion" pack.
Reboots are less frequent, but they still occur too often. They don't occur by themselves - its always when I'm using my phone.
It seems that it reboots more when its connected to my computer. The SD isn't mounted, but the simple fact that its connected seems to trigger reboots more frequently. Is this a coincidence or can a USB cord trigger reboots?
Help please
EDIT: The phone just made an audible cracking sound as it rebooted - like someone stepping on gravel. Hardware issue?
Hi,
Recently I have been having a problem with my G1.
When I have left my phone on stanby for a period of time and I press the menu key to turn on the screen the screen back light comes up but it's blank.
I have to press the end key periodically to get the screen to come on this can take anything from 5secs to 1min. I have reflashed and wiped several times and tried different themes but it still does it.
I am running cyanogen 4.2.15.1 with the enoch theme updated via cyanogen updater.
It does not do this all the time it did it more with Darkstar.
I have been told I should re-root but I am worried about doing this because I am on the new radio and have been told I cannot flash back.
What to do???
Then why don't you just change roms and see if the problem still consists :S
Jonnibravo said:
...worried about doing this because I am on the new radio and have been told I cannot flash back.
What to do???
Click to expand...
Click to collapse
DREAIMG.nbh will over-write you radio and spl, no worries there if you wanted to go that way but I think it's a little too extreme. What you need to do is a complete wipe and stable rom with no a2sd or swap. Once that's running for you - start adding stuff 1 at the time. Sooner or later you will pinpoint the problem.
Good luck.
borodin1 said:
DREAIMG.nbh will over-write you radio and spl, no worries there if you wanted to go that way but I think it's a little too extreme. What you need to do is a complete wipe and stable rom with no a2sd or swap. Once that's running for you - start adding stuff 1 at the time. Sooner or later you will pinpoint the problem.
Good luck.
Click to expand...
Click to collapse
Ok I reformatted the partition and set it back up using amon ra 1.5.2 swap 96 ext 512 then installed super d 1.10.2 and slowly added apps to my a2sd, did on Friday no problem till Thursday afternoon it once again I pressed menu and the screen stayed black after pressing the end key repeatedly it came back up about 30 seconds later.
2 theories here
Could it be because I am using a class 2 sd card or
Could it be related to a lock screen, before I used lockbot though I uninstalled it it still happened noww I am using lock screen 2.0 the day after it started happening.
Cyanogenmod has always done this on every version I've flashed. Try a different release.
goldenarmZ said:
Cyanogenmod has always done this on every version I've flashed. Try a different release.
Click to expand...
Click to collapse
I am on super d 1.10.2 not cyanogen, do you mean a rom that does not use cyanogen guts???
hey i've also got this problem but it's kind of different, 1 im not running cyanogen, 2 it might be a hardware issue with your's as it is one with mine. So far i think its the flex cable but not too sure. My screen would go black and whenever i try pressing the home or something the device would just completely shut off. I would remove the battery and have to try and boot it up at least a couple of times before it decides to work properly.Any ideas? i might get a new flex cable but im not sure if thats the real problem.
Jonnibravo said:
I am on super d 1.10.2 not cyanogen, do you mean a rom that does not use cyanogen guts???
Click to expand...
Click to collapse
Super-D does use few CM bits and pieces in his rom but that's should not be the problem.
Do you use any home replacement apps?
Do you use a task manager?
If so, make sure that your taks manager is not killing your home. Do make sure that it kills other memory intensive apps when not in use
If you use stock home then make sure to check "Keep Home in memory" in the "Spare Parts", see if that helps.
Sounds like either a memory leak somewhere (one of the apps) or a hardware problem. Let's hope for the first.
And yes.... please get rid of that class 2 card ASAP. New class 6 8 Gb card is around $15 and will last your thru few devices so its a money well spent.
Good luck.
I pretty certain it's not a hardware problem as there is no pattern to when it happens, I do have a habit of installing different home apps as I like to try them all that could be the problem.
]I give that a try
Try cleaning the cache . Maybe there are too many things running in the background .
how bout you do a full wipe and try out super cdsi v4 rom its just about the fastest rom out there
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues