[TESTING] - NAND OMGB (1.2.3)

[anish88]

Originally Posted by arrrghhh

Hrm. I know HD2 folk ran into some SERIOUS issues with different radio versions when they went NAND, and basically flashing a specific radio was part of flashing the ROM instructions.

For CDMA, perhaps this is necessary (this will be fun to troubleshoot for GSM...) So to all those having weird stupid issues with screen wakes, or really anything that hasn't already been confirmed as a bug - update to the 2.37 VZ radio, DO EEEEEET NOW!!!

i seem to be still having these weird screen issues. they didnt happen for the first 6 hours that i had the radio updated and then they came back today four times.

[[ACL]]

Originally Posted by anish88

i seem to be still having these weird screen issues. they didnt happen for the first 6 hours that i had the radio updated and then they came back today four times.

Its time my good man that you adb and harvest some logs. Just adb shell and do the following after replicating the issue

dmesg > /sdcard/mypoopylogs.txt

Then do the following but copy and past the contents to a file.

logcat -b radio

Once this is done we can begin to dive in again.

[anish88]

Originally Posted by [ACL]

Its time my good man that you adb and harvest some logs. Just adb shell and do the following after replicating the issue

dmesg > /sdcard/mypoopylogs.txt

Then do the following but copy and past the contents to a file.

logcat -b radio

Once this is done we can begin to dive in again.

next time the screen doesnt respond i will get the logs for it.

[muziling]

Screen not wake up, logs from last night
kmsg has one line

Division by zero in kernel.

[[ACL]]

Originally Posted by muziling

Screen not wake up, logs from last night
kmsg has one line

This is a known issue and ive been looking for it for a while. I cant seem to locate it. Everything on the log points to "htc_get_batt_info" but i dont see any division over there.

Also i notice this only happens while charging. Wonder if charginign is killing the panel ..

anyways your issue is not like anish. Your kernel logs look clean and there is no msm_fb time outs. Maybe the next kernel will help you too ..

[anish88]

for some reason in adb im getting device not found. do i have to have some special driver or am i suppossed to do this in the blue screened loader?

[arrrghhh]

Originally Posted by anish88

for some reason in adb im getting device not found. do i have to have some special driver or am i suppossed to do this in the blue screened loader?

If you've never used adb, threads that say TESTING probably don't apply to you.

Please read the FAQ on how to setup ADB. You need to recreate the issue and pull logs while in Android.

[anish88]

Originally Posted by arrrghhh

If you've never used adb, threads that say TESTING probably don't apply to you.

Please read the FAQ on how to setup ADB. You need to recreate the issue and pull logs while in Android.

I've used adb before arrrghhh. I had to use it with fastboot too. But for some reason its not. Recognizing it.


edit: seemed like there was some problem with the drivers. I got it up and running. Ill wait for another failed screen wake and post.

[Starfox]

Originally Posted by arrrghhh

Well the problem is, even if CDMA service isn't active, it'll still connect to towers. I have two Sprint phones that are service-less, but they still connect to the towers. You can even "attempt" to make a phone call, but as stinebd likes to say all you get is the angry Sprint guy on the other end.

That's part of FCC requirement, in which any phone (even ESN blacklisted ones) are allowed to connect to towers, mostly to allow calls to 911 (and *2 in case of Sprint ones).

-- Starfox

[anish88]

ok here is the most recent failed screen on. the phone seems to wake up, the screen is just completely unresponsive.