Serious (dialer.apk?) bug in SS 3.5 P1 on my moto droid

[romiir]

There seems to be an issue with.... dialer.apk?

Soon as I press the call button, my screen goes black and my phone is non-responsive, the only way it wakes up is if I slide my screen open.

If I answer an incoming call, I have to pull my battery to rewake the phone.

This is running SS 5.3 with /data/ from 5.1.

I'm going to either take a nap or make a full backup and then do a full wipe install to test that way.

Either way, more to come, when I get a chance to update this thread.

----

Update: I went ahead and wiped data, cache, and dalvik, after making a proper backup. I then did an install of 5.3 from scratch, and then applied the latest patch. I then booted up the device.

My phone now stays awake longer during a call, but I believe its due to the timeout delay being set higher now, not due to it functioning properly. It seems the phone, once locked, wishes to remain that way, unless I slide my screen open. The power/lock button is ignored. It only happens in the phone dialer AFAIK.

Usually if I answer a call, even sliding the screen open won't wake the phone, I have to pull the battery after my call.

The google account setup wizard was the same way, it forced me to slide my keyboard open to setup my account, although this may be intended.

[romiir]

Bump, I did update the thread.

Also, when my phone is non responsive it continues to function, ie: I can continue to talk on the phone, and when my voicemail hangs up on me, I can hear the hang up sound, and my phone vibrates, but nothing will wake it up...

I'll also add that I'm familiar with Linux, and I know my way around the terminal, if there is anything I can do to assist in troubleshooting this process, I'm not familier with the android os specifics, but it is linux.. heh

Help! or I'm going to have to do a clean install of 5.1...

[ChevyNo1]

Romiir .. wish I could test for ya, but my D1 is no longer activated, so I can't make any calls on it ... anyone else having this issue??

[romiir]

I don't know whats causing it, perhaps there is another error in that hotboot code?

It's basicly like my phone stops responding to the power button. I went in and enabled the slide wakeup feature, and I can usually slide wake the phone with this happens, so its a minor inconvenience, though a few times I've pulled the battery. I don't have a bunch of incoming calls to test with, but the device is useable, just very annoying.

[ChevyNo1]

If it were an error in the code - I would expect that EVERYONE would have this issue - thus far it seems only you do. Don't understand how that is the case though ...

[romiir]

It occurs both with and without my /data/, completely clean install does it. I think I already said that, but there it is again.

I'm running the medium voltage 800 mhz kernel from 5.1 release. The current archive of this kernel on your website is corrupt, as I mentioned in the kernel thread Chevy.

[ChevyNo1]

The corrupt kernels have been fixed - give that a try again.

[romiir]

Alright, updated to the latest kernel, issue persists. Although I have new information I just found out. If I connect my phone to a computer, (and probably a wall adapter, but I haven't tried it) it will wake up, and after that its fine again. It only locks and will not unlock during a phone call.

[Darkseider]

This seems to be a common issue right now on GB ROMs for the D1. Pete's GPA15 does this sometimes as well. I believe I read somewhere that CM7 on the D1 does it too. Regardless of kernel.

[droidic]

While this is not a problem I'm having other problems I've had that couldn't be fixed by wipe and reflash have all been fixed by flashing oldest nandroid backup u have I still keep at least one froyo than wiping and flash from there.

Simply Stunning 5.3 GB 2.3.4 low voltage 1.2ghz