yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Dladu:
This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.
[G1 Android Development] dbhatesyou:
well if you're on linux and have it to where adb runs from terminal , just type

adb shell reboot

but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,

now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )

now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.

[just the basic]
[G1 Android Development] jamesd86:
i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.

I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.

Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.
[G1 Android Development] adamo86:
screen dosent wake up after pressing power button

i have same problem with my x7510.when i press power button it dosent wake up somtimes.i have to soft reset.
[G1 Android Development] Boomer1331:
Haha so I'm reading this going "I hope this **** doesn't start happening" then it does it ha. I actually am connected to my computer putting on a new update, am currently on the Cyanogenized Rom and have the USB connected. I had the green light LED on but the phone wouldn't turn on. I put on the new update and I'll see if that works but it just occured as I was reading this thread.

Quite ominous.
[G1 Android Development] maxisma:
It's because of cyanogens kernel.

Sometimes when your g1 goes out of memory, it kills systemprocesses like zygote...
[G1 Android Development] defconoi:
The weird thing with me is, I cannot ddms or adb when this lockup occurs, ddms says the device is offline, but sysreq/call menu power works sometimes, sometimes you gotta press these keys a few times or pull the battery, "this issue never happens when wifi is off"
[G1 Android Development] TheDudeOfLife:
you have proof on that? I haven't had a single issue with wifi and locking the screen. I've been on the hotel's wifi all day.
[G1 Android Development] maxisma:
He said it. I do not have a proof, but i only got this problem when using his kernel...

Because of that i removed his kernel out of my rom.

So you probably won't get this problem.
[G1 Android Development] defconoi:
There is no possible way to get proof, christ I cant even adb/ddms, I need something to keep a log

Yes I got this problem with dudes and cyanogens on 3 different G1's, all is well with older kernels
[G1 Android Development] TheDudeOfLife:
Well ****...guess it is time to revert to my kernel too. I'm using his because I haven't had time to compile mine lately.
[G1 Android Development] amlwaycooljr:
I have recently switched to a build that doesn't use cyanogens kernel (Virtududes Rogers) and have not had the problem all day which is quite amazing for me seeing as it used to lock up 4-5 times a day. I tryed most builds that have cyanogens kernel and my phone has locked up with each. Hopefully we will be able to find out what exactly is causing this problem in his kernel. Unfortunately I am not able to get any logs as the phone doesn't respond to anything until I pull the battery out.
[G1 Android Development] Jason Syn:
Same here, no way to get a log but Virtudude's Rogers works flawlessly. Glad to see TheDude on here recognizing what's going on, hopefully we'll have a lock free build of .5 soon!
[G1 Android Development] Janis:
Well, this is crummy news

I had this issue when running CM3.4 flashed from JF1.5.1, I just flashed to CM3.4.1 straight from RC29 hoping to solve.

The only thing I noticed is that it never happened while I was charging. It only happened after 4pm, likey when I was connected to my home Wifi, WPA2), but I can't say for sure.

It happened connected to home Wifi. CM3.4.1, with (OK, I know this doesn't add stability....) Snappy swapper, or whatever it is, Open Home, Better Cut, Better keyboard, SnapPhoto Pro, and CallRecorder installed. Everything else was RC29 fresh & totally formatted.

As an aside, I went to reboot, and got stuck in boot loop, which seems to be the norm for 3.4.1 for me. I've booted twice on it normally, and this is #5 for boot loop. Reflashed, and still in boot loop.
[G1 Android Development] dwang:
No wake issues with cyan 3.4.1 here.
[G1 Android Development] defconoi:
yea, I got the same problem with the wifi, and its wpa personal with aes encryption, when I disable the wifi I have no problems, test that, maybe the wifi driver is messed up
[G1 Android Development] joe v:
Ok but has anyone tryed to run the same Rome without apps to sd and have this same problem. I been running super hero 2 without doing apps to ex2 and it works fine.. ugh!! I know when I was using apps to ex2 somtimes it would even wipe my whole card even the ex2 its so waked out!! I also don't think its the wifi.. becouse I never use it.. man I hope there a fix for this..
[G1 Android Development] _nobody:
ive been having this same exact problem, finally. i thought it was only me
[G1 Android Development] TheGreenJester:
I'm using Cyanogen's 3.4.1 without any wakeup issues. I am using apps2sd with ext3. I always have wifi on (WPA when at home, no encryption at work). I have been using his roms for a good while now and have never had this issue.
[G1 Android Development] cyanogen:
I dont have any of these issues myself, but enough people seem to so something is going on. I wonder if it's because I use CFQ scheduler in my kernel? I will switch it back to anticipatory and make a 3.4.2 build later tonight and see if it helps.
[G1 Android Development] defconoi:
count me in on testing

tweet me @androidunleashd
[G1 Android Development] amlwaycooljr:
I'd be willing to test it.
[G1 Android Development] djwaz:
I am down to test it out as soon as its ready.
[G1 Android Development] cyanogen:
I've posted 3.4.2 in my ROM thread if anyone wants to give it a try. It reverts the iosched to anticipatory and the tiwlan driver to 1.5r2.
[G1 Android Development] amlwaycooljr:
Throwing it on my phone as I write this, I'll post back later with feedback. Hopefully this will fix the problem.
[G1 Android Development] cyanogen:
Another possible thing I can think of is the enabling of the ARM "K" extensions in the kernel. The CPU in the G1 is supposed to support this, but its one of the only other things that could be a factor. If the last changes don't do the trick, this is the next thing I'll try reverting.
[G1 Android Development] Janis:
Posted this in CM ROM thread

My-silly-but-hopefully-useful-test
[G1 Android Development] JakobFriedrich:
first when using cynagen when you boot up just let it do its thing don't touch it at all like if you have jf updater on your phone let it tell you that you have 6 or 7 possible updates before messing with the phone at all, and once that is done hit menu twice to unlock your phone than put it in standby mode than unlock and since ive been doing this my phone has never hung or froze or not woken up

i do this everyday cuz i turn my phone off at night it affects my partners sleep haha
[G1 Android Development] defconoi:
@cyanogen I installed your rom, its not happening right now but its totally random anyway, so i'll let you know whats up in the next few hrs, ive had it running for 1 1/2 hrs or so already and its doing great
[G1 Android Development] cyrusvn:
When I used The Dude's Cupcake1.3RC1, I had this wake up issue but now I'm running The Dude's Cupcake1.3RC2 and everything has been fine for the last 2 days. What the hell lol?
[G1 Android Development] defconoi:
well I went to sleep, and when I woke up and pressed menu a 100x's with cyanogens new rom, my phone didnt turn on, pressing call menu power 3 times rebooted it
[G1 Android Development] chrisoyh:
I have been using cyanogen's ROM ever since I have rooted my phone and upgrade to cupcake, and I have never had any issues with waking up the phone.

But when on 3.3.8, I do notice that there are times when my phone will slow down.

And on 3.4, it will randomly freeze. It's not a permanent freeze though. I just have to wait and eventually all those system dialogs will pop-up notifying me certain processes are not responding. I just have to select "wait" on all of them and the phone will come back.

One thing to note though is that I am still using HardSPL and not the newest SPL as most of you here seem to be using. Radio-wise, it is the latest version.
[G1 Android Development] defconoi:
what we need to do is have \--> Kernel Hacking-> Detect Soft Lockups enabled so it prints a stack trace, also how can we get the stacktrace without a serial cable? This is almost certainly a driver issue, whenever any of my linux systems locked up over the past 15 years it was usually a driver issue... We need more details/logs somehow, any ideas?
[G1 Android Development] cyanogen:
"detect soft lockups" is turned on.. It will print the stack trace in dmesg normally, but I have never seen this get triggered.
[G1 Android Development] cyanogen:
I did a bunch of testing today, and found a reliable way to make the phone crap out and reset itself. AUFS and UnionFS are causing this problem. I've decided to move away from this method of Apps2SD in my latest ROM, and use bind mounts instead (plus an enhanced settings app that tells you the space available on your ext partition too).

The jury is still out until we get some reports back from people who have installed 3.4.3, but I am pretty confident in this.
[G1 Android Development] defconoi:
good find, I look forward to testing it, I think you may be right
[G1 Android Development] Jason Syn:
Well I installed 3.4.3 the second it hit and had 10x the number of non-wake instances as 3.4.2...

I venture to say that I had to reboot my phone 5 or 6 times from the time I flashed it on till now. I didn't do a wipe before flashing it, I'll try doing a wipe and see if I still have the same issues but I have to say 3.4.2 was way more stable.

Will report what happens after a wipe, unless someone tells me it's pointless.
[G1 Android Development] defconoi:
I have not tested it yet, im running SuperHero v2 with no wake up issues
[G1 Android Development] Jason Syn:
Yeah but how slow is it after using for 48 hours? Hehe

I LOOOOOVE the hero ROM's but I can't believe how much they slow down after 48 hours of every day use...
[G1 Android Development] GizDrak:
Well I am running CyanogenMod 3.4.4 now and my wake issue seems worse then it was when I was on dudes roger rom. so I am confused on what is causing this issue :-(
[G1 Android Development] cyanogen:
I really need something more to go on.. Have you modified sysctl.conf? Are you able to get an "adb logcat" when the problem occurs?
[G1 Android Development] frozenfoxx:
Running your latest, Cyanogen, haven't experienced the issue in over 24 hours. It happened once to me back at 3.4.2 but not since. I have not done anything non-standard with your build, just a few widgets, no WiFi connections usually, and no sysctl.conf mods (really, it's fast enough as it is).
[G1 Android Development] cyanogen:
In my thread, we are finding out (thru a lot of experimentation) that a lot of the optimizations that work on desktops don't port over to a device like the G1, and in fact actually hurt performance or cause very odd behavior. I use wifi all the time and haven't had the lockup issue being discussed here, so I'm just trying to narrow down the cause.

Another idea, does the problem still occur if the phone is underclocked to 384MHz?
[G1 Android Development] GizDrak:
I will have to get you some more information later at work at the moment. I have noticed that I get the wake up issue a lot less when I unerclock it to 384MHz but I still get it from time to time even sitting at that.

(EDIT) I am going to do a totally wipe on my phone. and reformat my SDCARD and then do a fresh flash when I get home I will let you know if I continue to get that problem after that.(EDIT)
[G1 Android Development] killerbeesateme:
Has anyone tried disabling 3G?

Sorry I'm late to the party everyone, but I had this issue on JF RC30, before the new radio came out. It went away and has since returned since Cyanogens 3.4 series.

I'm testing it by going 2G only for today and I'm going to see if I have any lockups.

Previously when I had this issue, it was always occuring in areas of poor 3G reception. Like my phone doesn't wake on the arm rest of my couch at home (where I'm 1 bar, and it falls back to edge frequently), or when I'm at the office (I'm on the 20th floor and 3G can be sketchy sometimes), either on my desk or because i went downstairs to have a smoke.

I have no hard proof, just anecdotal evidence that it's radio related, ie it's locking up switching to 2g, or connecting to 3g while the phone is sleeping.

I saw something interesting happen earlier today on my train ride, where the phone tried really hard to lock up. I had both arrows on my 3G connection but the phone was non-responsive. I held the power button down to try to get the poweroff menu to show up, which it did, but after about a minute of everything being non responsive.

This may not help the conversation at all, but this is what I've experienced. It may explain why it's happening to some and not others, as it could be directly related to reception in your area.
[G1 Android Development] trevordbs:
ive noticed this too, now that i think of it, it always has happened with wifi on.
[G1 Android Development] elealty:
I think to have solved the problem.

I've always wake problem.

I've try with 2 gb sd with fat16/ext3 fat32/ext3 fat32/ext2 and nothing change.

Now with 4 gb sdhc fat32/ext2 works good.

IF someone try can confirm this.

Rom cyanogen 3.4.4

Last spl
[G1 Android Development] fleshdeep:
I am having the same problem on cy 3.4.4 but only with wifi on. Once it is off my phone doesnt not lock up.
[G1 Android Development] cyanogen:
Are there lots of widgets running when this happens? Is your SD card mounted? Anything else that anyone can think of? If someone can get this to happen while they have "adb logcat" running, that would be awesome.

Obviously people are having a problem, but I have never had this issue on my device so I am just trying to narrow down a cause.
[G1 Android Development] fleshdeep:
No widgets at all. SD card is mounted. I can try doing a logcat check later today when I have spare time.
[G1 Android Development] XmeccaX:
i think i found the solution

i been having this problem with some of the new Rom's and it wasn't till recently i found out whats been causing it.

it first started with Dudes' 1.3, when the phone goes to sleep i had to push the menu button 4 - 5 times to wake it up, and it was driving me crazy, but i just lived with it. But now i just switched to CyanogenMod 3.4 and also updated a lot of apps on my phone, 1 of those apps was SetCPU. With the new version their is an option to set a different frequency when phone it asleep, well me thinking smart thought to drop it to 128MHz. well when my phone went to sleep it didn't want to turn back on, started playing around with different frequencies and that's were the problem is, if u drop your frequency too much this will happen.

So i set it to 245 is the lowest and haven't had that issue since :D.
[G1 Android Development] RPG0:
I only had a freeze (took 10 seconds to get to the unlock screen) when i had swapper installed. and it made sense. if the unlock screen gets swapped to disk, it's gonna take a while to get it back in ram.

Maybe it's not related to what you are experiencing, but are you using swapper ?
[G1 Android Development] faaque2:
I have had 'hesitation' upon wake with cyanogens 3.4.2 build. Going to 3.4.4, the hesitation had completely gone away. I use a 16gb class 6 card, ext3 partition, and have multiple widgets running (calendar, forcast, music) with no issue. The only issue I had under 3.4.4 was that when I removed the battery while on, the first boot up did not show any icons on the desktops...but a subsequent boot cleared that up.
[G1 Android Development] lhenry2k:
SDcard no more mounted. change SD

I FINALLY SOLVED the wakeup probelm when wifi was on

the problem was the SD card itself , after the sleep the SD is somehow unmounted..

I cloned my SD onto another SD card and wow .. everythink ok

big tnx to "elealty" user
[G1 Android Development] wayne07:
I have been using cygan mod for around 10 days.. from v3.2 to the current v3.44.

I have the phone in "coma" since doing the root, this has happened more than 20 times over the 10 days period. A few things that i have noticed:

1. Wifi is activated probably 90-95% of the times i got this issue. Without Wifi activated, the phone goes into "coma" only twice.

2. The base area of where the trackball will feel "hot". This is without much application running, i presume the phone is searching for the wifi connection or trying to maintain the wifi connection.

3. The APP2SD might be a contributor because i didn't experience this problem initially (1+ day of usage).

That said, there are 2-3 times that the phone went into "coma" without wifi.

I hope someone resolve this. Cause i like cygan's mod :-)

I think i won't be able to get a logcat because the phone seldom went into coma when it is connected to either the pc or on power... i think
[G1 Android Development] Jason Syn:
Just to update everyone I have had the Coma issue with or without WiFi. My SD card always stays mounted in fact I just had to replace my SD and it's happening at the same frequency with the new 3.4.4.

I flashed the new Ramjet r7 and NO COMA ISSUES!! I loved Virtudude's but the speed was meh. Since flashing Ramjet's the speed is great, no Coma, I'm a happy ROM junkie!
[G1 Android Development] cyanogen:
I'm going to have a build out later today that will use kernel 2.6.29. I'd be very appreciative if you'd give it a try, at the very least to see if this issue is resolved for you. The problem with this is that the "coma" issue only affects a handful of people, I've never seen it happen, and I haven't seen any logs (yet) from when it's happening, so it's very frustrating. I'm hoping that 2.6.29 is the magic bullet.
[G1 Android Development] dwang:
I get the same tracebacks when I enable the swapfile.

Its not with the zygote, but with various applications that crash with the same tracebacks.

Doesn't happen without swapfile though.
[G1 Android Development] cyanogen:
Okay, so zygote is getting killed or hitting a sigbus (usually means unaligned memory access) for some reason. Yes this would cause your device to go into a 'coma' like state, but you should still be able to get in with "adb shell". Is this not the case? And if you CAN get in, can you get the output of dmesg? I want to know if it was the OOM killer or not. If you can't get in, it's something in the kernel, maybe the .25 patch I use is no good on ARM? In any case, lets give this some testing tonight when I release 3.5 with the 2.6.29 kernel.
[G1 Android Development] dwang:
I can make this happen pretty much on demand with swapfile enabled. I don't get into the coma state, but my phone does reboot. Let me get the dmesg for you if I can.
[G1 Android Development] cyanogen:
Looking at the kernel code in i2c-msm, it looks like it will try to reacquire the bus up to 200 times, then it gives up (causing "undefined behavior"). I used to see this "bus was busy" message a lot with AUFS enabled, but it's pretty rare now. I assume that it happens when there is heavy IO to the device. I'm not versed enough in the MSM hardware to know whats happening here for sure, though.
[G1 Android Development] dwang:
I'm pretty sure its happening when processes are being swapped to the swapfile.

Its only started happening since yesterday, wasn't happening before. I'm guessing my sdcard is starting to wear out?
[G1 Android Development] cyanogen:
Maybe, but it's hard to say. The entire system architecture is based around I2C. I notice these messages MUCH less frequently on 2.6.29, though.
[G1 Android Development] dwang:
I've ordered another sdcard so I'll test it out and see if it happens on it.
[G1 Android Development] overground:
I'm not sure which of your kernels Dude's using on which build, but I was getting frequent freeze/reboots using his 1.3 rc2. Flashing back to beta12/RC1 has fixed this issue. No matter what I try on those, I cannot reproduce the problem. I have never run a swapfile on sd.
[G1 Android Development] defconoi:
I just got a lockup this morning with cyanogen's 3.4.6, fresh install with wifi enabled, for the past week or so I had superherov2 installed with no lockups(but hero roms suck atm, too slow)
[G1 Android Development] cronin4392:
Yeah I'm also on cyanogens 3.4.6. I've been noticing frequent lockups. I've removed all widgets, I don't use setcpu, and the lock ups happen randomly; sometimes when I open an application, sometimes when I rotate the orientation, and sometimes while its in standby.
[G1 Android Development] defconoi:
my phone locked up 3 times today with 3.4.6, im going back to one of dudes older builds if I can find one(or a hero rom)
[G1 Android Development] cyanogen:
I *wish* I had these problems at this point so I could help you guys :mad:

I posted the CM-3.5 release, which has the 2.6.29 kernel. If one of you guys with the "coma" symptoms could give it a try and report back, I would greatly appreciate it.
[G1 Android Development] fleshdeep:
I *wish* i could report back with dmesg but I forgot my 2nd usb at work! I had the lockups without a swap file (well atleast no swapper app). I formatted my sdcard. I will try the new exprimental version tonight, but i cant post any adb logs until tomorrow IF it still comatoses.
[G1 Android Development] defconoi:
@cyanogen ok i got wifi enabled with 3.5 and connected to usb with logcat, if it happens you'll get a logcat log
[G1 Android Development] cal3thousand:
I'm having spots where the screen will lock and the phone will kick out and reload the OS (not a full boot)

This was happening like crazy with Dxtop installed (there's an issue with it right now), but I removed it and now I still get random freezes.

I'm on CM3.2 using Unionfs apps2sd
[G1 Android Development] Thats BS:
I had a lot of sleep, freeze and reboot issues on the Dude's 1.3r2, at least 3 a day. Switched back to Cyanogen, with the 3.4.6 I haven't had any problems. Been running it hard too. It seems different for everybody though.
[G1 Android Development] GizDrak:
I am running CyanogenMod Experimental v3.5 for 14 hours now and have not had a single wake up issue yet. this is the first time and weeks that I have not ran in to the wake issue I hope this finely fixes it for good.
[G1 Android Development] cyanogen:
That is very relieving to hear. Anyone else have good results to report? I know it's only been a short period of time but please let me know if this does the trick.
[G1 Android Development] wayne07:
can someone help explain what will happen if i run apps2sd with a class 2 8G SD card and ext3?

Been trying to find the answer.

i have two corruption so far in the same sdcard... may be related to the phone issue with the rom.
[G1 Android Development] renegadedj:
still having the stuck black lockscreen issues with 3.4.6

tried uninstalling any apps affecting wifi or power (keeping wifi off, uninstalled power manager full) it seems the suckness happens less, but it happens nonetheless still.