[TESTING] - NAND OMGB (1.2.3)

[[ACL]]

Originally Posted by muziling

3G data icon, "Up/Down" arrow not activity when data in/out.

Seems is kernel problem:
xda-developers - View Single Post - [DISCONTINUED][Jan 12][SD/CWM][HOT]JDMS 1.7 BETA Ultimate[DISCONTINUED]


EDIT: SOLVED, thx HD2 git: https://gitorious.org/~3dak/linux-on...232eeecf3f7387
in htc_msm_nand_defconfig, need to remove line, otherwise will be compiled to CONFIG_MSM_RMNET=y

i'll remove that line from the config for the next release. Forgot why it's actually enabled

[muziling]

Originally Posted by [ACL]

i'll remove that line from the config for the next release. Forgot why it's actually enabled

I apply that smd_tty.c patch, then it works well, no SoD, nobody told me SoD again.

Maybe enable RMNET cause SoD ,now we have down/up arrow blink again

Waiting ACL commit code to git server.

[[ACL]]

Originally Posted by muziling

I apply that smd_tty.c patch, then it works well, no SoD, nobody told me SoD again.

Maybe enable RMNET cause SoD ,now we have down/up arrow blink again

Waiting ACL commit code to git server.

I pushed this change and cleaned up the defconfig a bit.

[milda25]

I have installed new release this morning and twice during this day I completely haven't no sound (no ringtone, no mic and no speaker during call). I don't know why, but it seems that this issue depends on connect to usb or/and to charger. Only one way to solve this is reboot. Which logs is usefull for you (dmesg or logcat)?

Sent from my Touch Pro 2 using Tapatalk

[arrrghhh]

Originally Posted by milda25

I have installed new release this morning and twice during this day I completely haven't no sound (no ringtone, no mic and no speaker during call). I don't know why, but it seems that this issue depends on connect to usb or/and to charger. Only one way to solve this is reboot. Which logs is usefull for you (dmesg or logcat)?

Sent from my Touch Pro 2 using Tapatalk

Both, but probably logcat is more important.

Always best to err on the side of caution and just pull all three. GetLogs makes this VERY easy, plus includes a lot of other useful output.

[milda25]

Originally Posted by arrrghhh

Both, but probably logcat is more important.

Always best to err on the side of caution and just pull all three. GetLogs makes this VERY easy, plus includes a lot of other useful output.

Happened again. I'm sure now that this causing missed call. When my phone ringing and I didn't receive the call, phone has been connected to USB. I don't know if missed call cause same without conect to usb. Will test later. If this happen, phone don't switch to sleep (orange LED lights), even if I disconnect USB.
Here is log got a few minutes after this happened. Using GetLogs application.

Edit: Missed calls will cause complete loss of sound even if the phone is not connected to USB. If I make a call in this state of phone, the internal speaker is completely quiet. If I switch to the loud speakerphone, I can hear an electric sound.

[arrrghhh]

Originally Posted by milda25

Happened again. I'm sure now that this causing missed call. When my phone ringing and I didn't receive the call, phone has been connected to USB. I don't know if missed call cause same without conect to usb. Will test later. If this happen, phone don't switch to sleep (orange LED lights), even if I disconnect USB.
Here is log got a few minutes after this happened. Using GetLogs application.

Edit: Missed calls will cause complete loss of sound even if the phone is not connected to USB. If I make a call in this state of phone, the internal speaker is completely quiet. If I switch to the loud speakerphone, I can hear an electric sound.

In my humble opinion, missed calls are something completely different. I assume you mean missed in the sense that the phone never rings, you never get any indication of a call?

Perhaps it's a language barrier, but I'm not exactly sure what you mean. Hopefully ACL can make some sense of your logs...

[milda25]

Originally Posted by arrrghhh

In my humble opinion, missed calls are something completely different. I assume you mean missed in the sense that the phone never rings, you never get any indication of a call?

Perhaps it's a language barrier, but I'm not exactly sure what you mean. Hopefully ACL can make some sense of your logs...

No, I mean that all sound is OK, then the phone begins the ringing (incomming call). I don't accept this call and get the missed call (red arrows in status bar ) After that, all audio including mic goes to hell. I can simulate this whenever you want. Understand? Yes, language barrier is terrible thing

[[ACL]]

Originally Posted by milda25

Happened again. I'm sure now that this causing missed call. When my phone ringing and I didn't receive the call, phone has been connected to USB. I don't know if missed call cause same without conect to usb. Will test later. If this happen, phone don't switch to sleep (orange LED lights), even if I disconnect USB.
Here is log got a few minutes after this happened. Using GetLogs application.

Edit: Missed calls will cause complete loss of sound even if the phone is not connected to USB. If I make a call in this state of phone, the internal speaker is completely quiet. If I switch to the loud speakerphone, I can hear an electric sound.

This is odd.

01-31 21:27:01.970 E/ToneGenerator( 122): --- Stop timed out

So you are telling me the old lib's worked better ? f*ck that's the last thing i want to hear.

let me know if you need a copy of the old libs. If the old one works better then you can just replace the libaudio and libacoustic.

[milda25]

Originally Posted by [ACL]

This is odd.

01-31 21:27:01.970 E/ToneGenerator( 122): --- Stop timed out

So you are telling me the old lib's worked better ? f*ck that's the last thing i want to hear.

let me know if you need a copy of the old libs. If the old one works better then you can just replace the libaudio and libacoustic.

This problem I hadn't with previous build from 01162012. Thanks for the offer the old libs, I will stay with this new one. At least it will force me not to have missed calls.
And don't be discouraged, ACL, you are making a lot of hard work ...