[TESTING] - NAND OMGB (1.2.3)

[[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.

[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.

[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]

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.

[anish88]

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

[anish88]

another one

[[ACL]]

Originally Posted by anish88

another one

ohh man you have a very weird issue. Bottom line is your panel doesnt seem to be powering back up.

<4>[ 7836.208618] msmfb_pan_display timeout rerequest vsync
<4>[ 7841.219055] msmfb_pan_display timeout waiting for frame start, 21

This means that android is trying to draw but there is no vsyncs so that can only mean the panel never came back up. Unfortunately the logs you sent dont include the panel type which is usually in the early boot phases.

next time you adb just do this

dmesg | grep panel

This way i know which panel your rhod has. The good/bad news is that the next kernel tries to re-power the panel. But that doesn't explain why yours is dying to begin with.

ALso do you always keep wifi on? in the first log i saw wifi preventing the phone from going to sleep. Now sure if it's something you always have on or now.

Thanks for the logs. I'm hoping the next kernel will either help or give us more to look into it.

Also what apps do you have in? whats the following ?
d.process.media
.amip.ClockSync
com.bwx.bequick
id.partnersetup