Database Develop

Phone hangs in sleep mode

Hello there,
I really am stumped, and would really like some help! I've searched the forums, can't really find what I'm after, so apologies if this as already been asked/answered.
Basically, my G1 hangs a lot when it goes to sleep. I'm running Cyanogen 4.0.4 with an 8Gb Class 6 card - everything was fine when I was using the stock 2Gb card that came with the phone, but after having loads of trouble trying to transfer my apps, I decided to just wipe and start again. The card is Ext2 parted with a 293Mb size partition. I did have it as Ext3, but thought this might be the problem (since I didn't have any problems with Ext2 on my old card), and wiped and repartitioned as Ext2 but that wasn't the case and problems persisted. Occasionally the phone will hang when it is on, but mostly the hanging happens when I leave it alone for a while; the screen stays dark and nothing happens, and I have to take the battery out and restart the whole phone.
One thing to note is that when I did reinstall everything, MybackupPro often didn't like the card, and gave me 'I/O problems with card' or 'Cannot install app' mesaages until I rebooted and started again each time the messages came up. I had to reinstall my apps in 10 - 20 app chunks in the end, rebooting when errors came up, but eventually I got everything reinstalled.
I'm running Swapper (I know Cyanogen does something similar natively, but wasn't sure how it worked...someone please correct me if I shouldn't be using it), and Overclock Widget. Like I said. I never had a single problem before with my old card and these apps, so this all leads me to think it may be the card, but any advice would be much appreciated!

markdjj said:
Hello there,
everything was fine when I was using the stock 2Gb card that came with the phone
MybackupPro often didn't like the card, and gave me 'I/O problems with card' or 'Cannot install app' mesaages until I rebooted and started again each time the messages came up.
I never had a single problem before with my old card and these apps, so this all leads me to think it may be the card, but any advice would be much appreciated!
Click to expand...
Click to collapse
Hmm... sounds like the card to me. And the fact that you are using swapper on a possible defective card may very well be causing your system to hang. The system is relying on the sdcard as part of it's memory. So if the cards fails at any point, so will your phone. It'll be like pulling the RAM module out of your computer while your using it. Include a logcat of the phone crashing if you can and post it. Also reformat and check the partition for errors.

Thanks for your advice, I thought it may be the card too. Partitions seems fine...I used Partition Manager and it didn't throw up any problems.
As for Logcat, I did try and do that, but got a bit stuck trying to fiddle with my computer, and I don't think it's going to happen. I'm a bit of a newbie I'm afraid.
I don't mind getting a new card, but the only thing I'm concerned about is moving my apps...on this post here http://forum.xda-developers.com/showthread.php?t=553469 it looked pretty easy, but could you tell me if these commands are to be executed in the terminal on the handset? Does it copy the apps, because I imagined that if you fiddled with stuff that's in use (like moving an app from the Ext2) would cause a lot of FCs and possibly even hangs.

odd hang
I myself am getting a bit of a hang when waking the phone up, i have to hit the menu button several times, kinda reminds me of the coma issue that we had back on the old kernal. i didn't have a problem till i clean out my phone by wiping and reformating my card, it is not that big off a deal but it is just strange. oh and to the op, you do not need to run openclocker since cyanogen's rom has cpu scaling that does it already and if you have your partions in order as fat,ext,swap than it will auto use compchace

gridlock32404 said:
I myself am getting a bit of a hang when waking the phone up, i have to hit the menu button several times, kinda reminds me of the coma issue that we had back on the old kernal. i didn't have a problem till i clean out my phone by wiping and reformating my card, it is not that big off a deal but it is just strange. oh and to the op, you do not need to run openclocker since cyanogen's rom has cpu scaling that does it already and if you have your partions in order as fat,ext,swap than it will auto use compchace
Click to expand...
Click to collapse
My phone did the exact same thing when I was using either Jac's Hero 1.3 or cyanogenmod 4.0.1. I tried everything and it wouldn't go away so I ended up switching to xrom.

Since cyan has been doing a lot of kernal tweaks lately do you think that it is possible that the coma issue has gotten reintroduce though, I mean both mine and the op is doing it, his is worse but if you remember that is what was happening to a lot before, mine never got to the point of pulling the battery but to the point of annoyance just like it used to

How is the xrom <that's jac's non hero build, right?> is it comparable to cyanogen's, I love cyan's performance but if this persits, I might find something else for awhile

I love it honestly. He just updated it to 1.4r3 and its is sweet, it has a custom theme and it looks really good. The performance is great and I don't even use a swap with it. I tried cyan again when 4.0.3 came out and only used it for 2 days before switching back to xrom. Personally I liked the icons and lockscreen of xrom 1.3r3 better then 1.4r3 but that is just my opinion, If you want to try 1.3r3 I can send it to you since it's not up anymore. Try 1.4r3 first though and see what you think because IMO it is the best rom out. Hero is nice but no matter what you get some lag and after a week or to it gets slower so I don't use it yet, I try the new builds but never stick with them.

Yeah I feel the same way but the hero builds too, nice to play with but nowhere near usable for me, I might just have to check out the xrom but I don't wanna give up loccy's browser, it is just friggin sweet and it works good for me because of the option of viewing just destop versions of sites since I get the men's health daily newsletter and whenever I would click on a link it would give me the moble version and not the article I would like to read, if loccy's brower works on the xrom, we might just have a winner

I haven't tried it yet so I'm not sure. Is it just a simple .apk to install or do I need to push it?

I just read the thread on the browser and it says it should work on xrom. It says to push it but I have just installed it like a normal apk before

Yea I am downloading it right now so I will let you know how it goes. Just so you know the browser on xrom doesn't have those zoom in/out buttons that pop up when you touch it, also it has multi touch just no double tap to zoom. I don't see any settings for turning off mobile pages though.

Well I am downloading the xrom right now so I will be flashing within the next half an hour or so, let me now if the browser works for you, by the way is compchache or swap automatic on it like cyan's or do I need to set it up myself, I perfer swapper, it just seems to work better for me

I think swapper is automatic but to be honest I never have used it for xrom because it is fast enough without it. The better browser works I just installed it normally, no pushing and I am using it right now with no problems, you have a pm.

If you like the notification bar icons in the first picture on the xrom thread they are from 1.3r3 because they changed in 1.4r3. If you want the older ones I can give you that rom amd it runs just as fast, only has a few differences from the newer one.

This xrom is nice, I am happy with the newest, oh and when I installed swapper and went in it was already set at 96mb and swappiness of 80 and I am on a fresh install and reformat so it must be automaticly set to then, explain why it is so smooth. Definitely comparable performance wise to cyanogen so I might have to stick with this for a while

I dont even have a linux-swap partition on my sd and I haven't had any problems with speed or lag.

Mine is silky smooth, better than I have had on any roms even the stock one

G1 not working very well anymore?

okay, so i've had my G1 for about a year. i have played around with it a lot and as recently as a month or so it has been very snappy and responsive with SuperD rom as well as older (4.x) Cyanogen roms. i have flashed cyanogen 5 test-something (-2 maybe?) and didn't really like it, so i tried a couple of the other newer roms. now, it seems like no matter what rom i flash, it has serious lag and responsiveness problems. i have done complete wipes (partitioning the SD card to fat/fat32 only, wiping it completely with a disk wiping utility, re-partitioning with amon ra recovery, and wiping from amon ra recovery), i have installed both new and old roms, i have flashed old and new radios (i have had danger spl for a while), and nothing seems to help! i am getting the HTC Evo on Friday so i guess this doesnt really matter that much, but i am concerned that other people might be having this problem and if i give this phone to a family member or friend i would like it to be functioning as smoothly as possible. it seems like since my hardware hasnt changed, i should be able to wipe, flash my old setup and have nice snappy response time like i had before. right now it's like i open the web browser and load a page and then press the home hardware key and it takes about 5 seconds for the homescreen to load, even though all i have is four icons, the default background, and the power control widget. there used to be no lag at all with this same configuration (an older Super D rom). any suggestions?

i'll just say amen to that. my G1 just isn't what it used to be anymore. I just recently did a complete wipe including completely clearing and repartitioning the SD card and I didn't even bother reinstalling all my apps, i'm just reinstalling them as I find I need them... don't have a lot of widgets... things just aren't what they used to be anymore. i wish i could figure out why. and i'm in contract until NEXT july... so i'm gonna have to figure this out sooner than later.

Same here, but it got a lot faster as soon as I added overclock and removed beautiful widgets!

Agree with the others posted. I do not use beautiful widgets. So that was not the issue with me.
I have also noticed that my internet speeds with t-mobile have dropped in half for the last few months. They (t-mobile) do not provide any real help on that issue. I remember back in '08 a post being made that they will put people on low internet if they exceed the 1Gig download in a month. Has anyone every ran into that one?

I'm not that tech savvy or anything, but you guys do know that just about everything you flash to your phone says "Caution not responsible this will put your phone under major stress... wear and tear... blah blah blah"...
Mine did the exact same thing. I always just assumed that after trying to push it to it's very limit for so long it finally just gave up and couldnt go that far anymore.

This is true. My G1 is having weird problems. I have overclocked before, but not anymore. I think these problems started after I overclocked, or after I flashed the latest radio for the G1.
Developers just write that their ROMs will put the phone under stress just to warn people that their not at fault for their phone screwing up miserably somehow (like with the catastrophic Haykuro SPL... oooo ****, what a mess that was)
When the Haykuro SPL came out, I didn't immediately flash, even though I had the required radio already. I made a few posts in XDA verifying the steps so that I wouldn't **** my G1.
And clocking the G1 to 528 Mhz ISN'T OVERCLOCKING.... the processor was made to go up to that spec, HTC just kept the maximum clock in Android to 384 Mhz to save battery and prevent complaining customers.
The G1 should be able to write it's NAND over a thousand times... it's a flash memory chip, it was made for read/write. It won't get slower unless you really screw the crap out of it, for example, by applying more voltage to the damn thing.
Maybe I should re-flash the radio, the SPL, and erase and flash the recovery and everything else. Or maybe return it to complete stock and bring it back to rooted-ness... that can solve some small little mistake I possible made a while back, in the first months of G1 rooting...

AustinAce said:
Same here, but it got a lot faster as soon as I added overclock and removed beautiful widgets!
Click to expand...
Click to collapse
Overclocking is great
But the G1 should still have the same performance as it did when it was manufactured. The CPU is the same, everything is the same. I don't know why it seems like the G1's performance is diminishing... maybe it's just our exposure to superior Android phones like the Motorola Droid or Nexus One?

For all of those that are complaining about their slow G1 devices on Cyan's 5.0.7 turn off swap and compcache. Confirm it with adb shell and type "free" to confirm that it's reading 0 for swap. Adjustments have been made so that you shouldn't need it anymore. Cyan has said himself that you would be digging a "swap grave" if you did. Also, I find it funny how a lot of people b!tch that the G1 won't be upgraded beyond Donut but clearly we can all see why. My suggestion is to turn off swap and compcache. Not good enough? Go back to stock or whatever you were happy with and stop complaining!
For the record I (like thousands of others) have 5.0.7 on my G1 (without swap or compcache) and it's been running fine. Overclocked and all. Using ADW Launcher with 7 screens filled with widgets and shortcuts. I was running it for 3 days straight with heavy usage before it rebooted on me. So I think that it's something that you're doing.

Everytime my G1 has acted up and no amount of recovery and sd card wiping seemed to help. What did help me out though was wiping from fastboot using the
fastboot erase boot
fastboot erase cache
fastboot erase userdata
fastboot erase system
commands. This will wipe everything in the phone (outside of the sd card).
It should actually perform the same wipe functions as the recovery program does, but I have had luck with this in the past.
BTW, I fried one of my older G1s overclocking it when Cyanogens roms first came on the scene. It just became completely unstable and would shut off randomly and frequently. Unless you've done some hardware damage due to stress or clumsiness, your G1 should be rock solid as Binary says.

Why does my G1 seem to get slower and slower
T-mobile G1 32B Bronze "PVT Dream"
Extended Life Battery and Cover
16 GB Class 6 Card, ext4 1024MB, linux-swap 512MB, remainder fat32, No Compcache, Apps2SD - "before GAPPS"
Cannon202 2.2.1 build, 2.1 firmware, 2.22.23.02, Tried w/wo cpu oc app and Cannon's original build is Superior, would not rec installing oc app at all. The clocking used in this builds kernel is smoking fast, yet made to be unstable imo in my tests against this build with the cpu overclocking app, customizable yet much slower, flakier, and noticeably unfavorable temp increase just holding it ...
My G1 is smoking fast, Great Signal Strength, Excellent wifi and 3G speeds. Things I've noticed in my journey into the "Custom Rom Universe."
1. All it takes is one file,app, or architectural flaw (ext234,Linux-swap,corrupted partitions, faulty cache etc...) - even slight - to destroy the Harmonious bond between software and hardware on any device.
2. Most new phones are coming with Class 2 removable storage from the OEM. A Class 4 card may suffice, but a Class 6 Card is mandatory. If there were faster I would say go even faster on the transfer rate. depending on the application, the Android OS will bounce to and from the SD Card a bunch and more often as more apps are installed (updates), cache, partitions, etc the faster the card the less the phone has to compensate against the slower transfer rates, thus better performance ...
3. Heat/Battery - I tied these together why? Heat from Over-clocking or even just Summer weather or the combination of the 2, kills batteries overall life and output. Not to mention the affect on all electronics from heat, the cooler the better I would assume. If your phone has a custom Rom another factor to take in consideration is the it's going to require more juice from the battery and the change in the amount of load across the board on the phone as it does any pc/mac or any other form of computing device is pull more power which can weaken, damage, or even kill the battery all together. It's amazing how much the integrity of the battery affects the overall performance.
("IMO") - I just thought I might add my 2 cents. The performance on my phone is outstanding and very stable and I have changed the architecture so many times ... I would be embarrassed and damn near ashamed to venture a guess and disclose that information . So like it says "In my opinion" it's alright to disagree . The point is to argue, not to be argumentative , but I thought this information might help someone. Sorry for the long post.

Have you tried putting a new class 6 MicroSD card in? That might be the problem. SD cards only last so long.

SetCPU resets on Boot

I am running setcpu on a Droid wit Froyo. It works great except that each time I reboot, I need to reset the clock speed. I am running a 1000 kernal, set at 800. Will stay like that till I boot, then always goes back to 600.
Is it just me or am I missing something.

It's not just you. Mine does the same thing (resets to 600) when I reboot, and it's been doing it ever since I installed Froyo. Unfortunately, I don't know the solution yet. When I get it - I post on other forums too - I'll post it here.
-Mike

Be sure that your Set CPU is on the phone and not mounted on the SD card. I went back and checked mine and it was on the SD card, but I had not moved it.
Anyway, that solved the problem for me.

When screen goes into sleep, never again wakes up!!!

Something weird is happening to my Captivate.
I flashed updated from Apex 9 to 9.1 with a full wipe on Tuesday I think. After that, when my phone is just sitting there and the screen goes to sleep everything is fine, but if I leave it sleeping a long time, say 30 minutes give or take, when I try to wake it up, the soft keys light up, but the screen won't wake, I can't do anything but remove the battery to reset the phone. Today I flashed newe ROM (Sensation), New Kernel (Talon 4.3 - 1200) and new Modem (JW2). Went to the kitchen to get a bowl of cereal, I saw the softkeys on (was chatting with my wifey) and tried to wake it up, same thing.
Anyone going through something even near as weird?
I'm thinking it can be the lockscreen, honestly haven't tried, but just changed it to MIUI to see. If it does it again, I will try waking it up and sliding the lockscreen in the dark. Will keep you guys posted.
If anyone has a solution or knows what the issue might be, I will be very grateful, still saving for the SGSII.

vette95 said:
Something weird is happening to my Captivate.
I flashed updated from Apex 9 to 9.1 with a full wipe on Tuesday I think. After that, when my phone is just sitting there and the screen goes to sleep everything is fine, but if I leave it sleeping a long time, say 30 minutes give or take, when I try to wake it up, the soft keys light up, but the screen won't wake, I can't do anything but remove the battery to reset the phone. Today I flashed newe ROM (Sensation), New Kernel (Talon 4.3 - 1200) and new Modem (JW2). Went to the kitchen to get a bowl of cereal, I saw the softkeys on (was chatting with my wifey) and tried to wake it up, same thing.
Anyone going through something even near as weird?
I'm thinking it can be the lockscreen, honestly haven't tried, but just changed it to MIUI to see. If it does it again, I will try waking it up and sliding the lockscreen in the dark. Will keep you guys posted.
If anyone has a solution or knows what the issue might be, I will be very grateful, still saving for the SGSII.
Click to expand...
Click to collapse
are you Overclocking or Undervolting. That could be the problem, happened to me once. try higher voltage or wipe voltage settings in recovery.

kant5t1km3 said:
are you Overclocking or Undervolting. That could be the problem, happened to me once. try higher voltage or wipe voltage settings in recovery.
Click to expand...
Click to collapse
Nope, have it at default speed and voltage.
I will still try wiping the voltage settings, because I remember OC/UV when running Apex 9.0
BRB, let me try...
Ok, just did, I'll let it rest there for about an hour...
Will keep you posted.

just a though but also try wiping data/cache/dalvik

kant5t1km3 said:
just a though but also try wiping data/cache/dalvik
Click to expand...
Click to collapse
Yeah, I wipe everything before flashing always, the only thing I never wiped was the voltage settings, it just might do the trick.

vette95 said:
Yeah, I wipe everything before flashing always, the only thing I never wiped was the voltage settings, it just might do the trick.
Click to expand...
Click to collapse
ok... keep me posted

Having the same problem from time to time
i was once told that keeping pressing the soft key would wake the screen up when power key couldnt work
that method sometimes does work for me
however,mostly,it makes no sense 8
regards

It stopped doing it.....
It hasn't happened anymore since I wiped the voltage settings. But now, every now and then it just like soft reboots, it's weird. I hear the boot sound all of a sudden without any apparent reason.
New challenge.

Well, went back to APEX 9.1, hopefully this will solve the soft-reset issues I was having.

vette95 said:
It hasn't happened anymore since I wiped the voltage settings. But now, every now and then it just like soft reboots, it's weird. I hear the boot sound all of a sudden without any apparent reason.
New challenge.
Click to expand...
Click to collapse
Same thing happened to me on dlevs rom. I thought it was a processor not getting enough power thing so I just let it go. (I do extreme under volting
Sent from a phone controlling a computer controlling a different phone

sepherian said:
Same thing happened to me on dlevs rom. I thought it was a processor not getting enough power thing so I just let it go. (I do extreme under volting
Sent from a phone controlling a computer controlling a different phone
Click to expand...
Click to collapse
Under volting the processor on these phone will help you very little as far as battery life goes. The screen is what drains the battery like crazy. Your probably causing more harm by extreme under volting.

This is what one of my friends captivates kept doing on the stock froyo rom and the only fix that I found was flashing a different 2.2 rom over it.

Help diagnosing freezes and random reboots

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