A further explanation. About 1 week ago I had to doctor my phone after it stopped showing text in emails...I had one app (maps) that the Palm profile restoration program said that the download failed. Repeated trying to download with same failure. The Palm restore that happens when you log in after a doctor visit is pretty relentless in trying to replace everything that it has backed up from your phone. It will continue to retry downloads, it usually asks if you want to retry. I think maybe the Palm profile restore was still trying to do something. I finally told it to not try to download that map app any more and I think that was what stopped my phone from going on and off by itself. I had also bypassed logging in to a couple of accounts such as facebook and Skype. It also remiinds you that you have not logged into these accounts. Wish I could remember, but whatever I did was a simple thing and definitely was not hardware related. I am using my pre2 (2.2.4) on sprint. I do not remember if it wanted to install the sim or not. If it did I disabled that as well. If I ever remember what I did for sure, I will let you know.
Right, that makes sense. The phone in that case is being woken by notifications of the failed download.
For the problem at hand, what if Luna is disabled, the screen manually turned off, and a logging thing attached to powerd or something that can detect button presses of system activity?
I suppose i'll go and look for the thread that talks about the deep sleep mode, where it was discussed in the context of dismal battery life on certain Pre3's. Testing for the deep sleep failure condition is pretty straight-forward (you keep the command line window open [wTerm? don't know if wTerm supports phones] while logged in as root and watch for the kernel messages about going into standby) and a fix was also provided in the same thread.
This might not be the exact problem and the fix might not be the perfect cure, but under webOS, services are "sleeping" in the background until activated by an event or a timer, and your issue definitely involves a service process that wakes up to do its thing, fails and then comes back on on a timer. Most likely the hardware is returning a signal that cannot be gracefully handled and the service is not written to permanently fail after a certain number of tries. Deep sleep failure is exactly like this (except for the screen activation) and is we could somehow "knock out" services individually, it would be possible to see what's failing and patch it.
If the Doctor isn't doing its job and it is possible to force-reflash firmware (i've seen that happen with modem firmware) this might also be another way to go, but like before, i do not promise anything... just troubleshooting.
The unit is definitely defective, but don't lose hope, because i'm very much interested in making it work and will do my best to help you, even without a very deep kernel and OS knowledge that some others here have. I'll try to find the deep sleep thread and the modem firmware fix thread, and we'll later see what else can be done to pin down the issue and force-fix it
Edit: ...found the modem reflash thread. It's not the solution to your problem, but a "proof of concept" that firmware can be reflashed outside of the regular doctor (corrupted modem, fixed)
Edit2: forund a thread regarding the sleep problem, might not be the same one, but i don't have time now... Pre Will Not Sleep
In this thread it mentions Nodoze as the fix, so try it and let us know
Thanks, but this is way over my head... I am not a Linux person at all, and everything you mention, plus those other threads all go with "we did this" but without any info about "how it's done" in the first place...
I don't have a clue about command lines and such. In the search "Just type" line???
Palm M105 > M130 > Zire 71 > Zire 72 >TX > Lifedrive > Pre > Pre2 >Touchpad > Pre3(8GB) > Pre3 (16GB)
I see a pattern...