[ROM] CyanogenMod 6.1 [Beta2 - 05 Feb 11] & 7 [Beta3 - 11 Feb 11]

[Guest droweed]

I have on Cm7 beta 4.1 still blank screen after calling, any fix for it????

without this fix phone IS NOT USABLE! many peoples write about it, but where are no comments about this from developers!

its not yet fixed, better wait for it, or use another rom

[Guest]

I have on Cm7 beta 4.1 still blank screen after calling, any fix for it????

without this fix phone IS NOT USABLE! many peoples write about it, but where are no comments about this from developers!

Does it do this if you go to call settings and select keep screen awake?

[Guest RipZ]

Does it do this if you go to call settings and select keep screen awake?

this not helps

[Guest harry_m]

this not helps

it does for me!

[Guest Simon O]

this not helps

And your post does not help either. Write a bug report on the github if you want it to be seen by the developers. This thread moves too quickly.

[Guest]

And your post does not help either. Write a bug report on the github if you want it to be seen by the developers. This thread moves too quickly.

Flibblesan,was wondering if USB tethering is working in beta 4.1.

Like you said things move fast on here so hard to track all things.

I tried using it,but seems to be broke,I also deleted my drivers and reconnected to see if it was drivers but no luck?

Edited February 15, 2011 by Guest

[Guest timsewell]

Hi. First time comment and getting on very well with the latest 4.1 CM7. I've had the proximity sensor issue as well (in fact it's the only major one I've come across) so I popped over here: https://github.com/TomGiordano/android_devi...te_blade/issues and voted the bug up. Can I suggest that everyone else experiencing it does the same.

[Guest Simon O]

Flibblesan,was wondering if USB tethering is working in beta 4.1.

Like you said things move fast on here so hard to track all things.

I tried using but seems to be broke,I also deleted my drivers and reconnected to see if it was drivers

It seems to work ok but I've not had much chance to test this yet. I'm currently trying to get the wifi tethering working correctly.

[Guest Simon O]

Hi. First time comment and getting on very well with the latest 4.1 CM7. I've had the proximity sensor issue as well (in fact it's the only major one I've come across) so I popped over here: https://github.com/TomGiordano/android_devi...te_blade/issues and voted the bug up. Can I suggest that everyone else experiencing it does the same.

Could I also suggest that people please try and obtain logs from the phone covering the times when the call started and ended so we can look for any errors. Might give an idea what the reason for this is.

[Guest timsewell]

Could I also suggest that people please try and obtain logs from the phone covering the times when the call started and ended so we can look for any errors. Might give an idea what the reason for this is.

Tell me how and I'll be happy to next time it occurs (also please advise to whom they should be sent).

[Guest Tarot]

Thanks, Flibblesan, for your ROM.

Another minor bug - Battery voltage is incorrectly displayed.

All programs can be transferred to an SD card - bug?

Edited February 15, 2011 by Tarot

[Guest skyhacker]

just to be clear here, i'm getting the issue where the screen doesn't wake by itself on call end but is I press the sleep button it does wake up and works I don't need to remove the battery, I'm seeing some people that need to remove the battery for the phone to work again, can you tell me if there are 2 diferent bugs or it's the same to all, just to clarify things

[Guest zata]

Power button is working for me only for max 2 sec after call, when I wait longer phone will not wake up and I have to remove battery or plug in USB cable :D

[Guest robng15]

just to be clear here, i'm getting the issue where the screen doesn't wake by itself on call end but is I press the sleep button it does wake up and works I don't need to remove the battery, I'm seeing some people that need to remove the battery for the phone to work again, can you tell me if there are 2 diferent bugs or it's the same to all, just to clarify things

I installed the 4.1beta this morning, and am extremely happy... having read through the forum I was a little concerned about this issue, but every call I have made the screen has come back to life on call end.

Angry Birds, on phone mem, runs like a dream... better than any other ROM I've had on this phone.

Cheers

[Guest targetbsp]

Is Angry Birds the only game that doesn't run off the sd card or does nothing run off the sd?

[Guest robng15]

Is Angry Birds the only game that doesn't run off the sd card or does nothing run off the sd?

There are quite a few "games" "emulators" that don't work... they apparently are using native code... co-pilot, which I thought did use native code, does run very well from the sd-card

[Guest fonix232]

Could I also suggest that people please try and obtain logs from the phone covering the times when the call started and ended so we can look for any errors. Might give an idea what the reason for this is.

Problem is that the light sensor is mis-calibrated. Maybe it was posted here, maybe in the build topic, but in the CM7 settings/Display/Auto light sensor menu you can set the light sensor's settings, and all value was given. After that fix, after-call UI will work properly.

EDIT

Found it, it is in this very topic, comment #918 by Victor von Zeppelin!

Edited February 15, 2011 by fonix232

[Guest exec]

Problem is that the light sensor is mis-calibrated. Maybe it was posted here, maybe in the build topic, but in the CM7 settings/Display/Auto light sensor menu you can set the light sensor's settings, and all value was given. After that fix, after-call UI will work properly.

EDIT

Found it, it is in this very topic, comment #918 by Victor von Zeppelin!

Thanks, the info in that post fixed my problems with black screen after calls. :D

[Guest thecoming]

As a follow up to my handcent SMS not working. Like angry birds, it was because I installed It to the SD card by default. By moving it to internal it was fixed. I hope this helps others and helps to fix the problem.

[Guest metzench]

Problem is that the light sensor is mis-calibrated. Maybe it was posted here, maybe in the build topic, but in the CM7 settings/Display/Auto light sensor menu you can set the light sensor's settings, and all value was given. After that fix, after-call UI will work properly.

EDIT

Found it, it is in this very topic, comment #918 by Victor von Zeppelin!

I´m already integrating these values in my build right now, hope it works.

[Guest Smiff2]

I installed the 4.1beta this morning, and am extremely happy... having read through the forum I was a little concerned about this issue, but every call I have made the screen has come back to life on call end.

Angry Birds, on phone mem, runs like a dream... better than any other ROM I've had on this phone.

Cheers

so 'stuff' is faster now than most 2.2 ROMs? very impressive if that's true in general already..

i assume setcpu works ok with this too?

edit: ah no see assuming has made an ass out of me :D

Edited February 15, 2011 by Smiff2

[Guest Simon O]

Yup, spotted that earlier and fixed. I've submitted it to Tom.

[Guest Simon O]

i assume setcpu works ok with this too?

No as the kernel currently has no overclocking features.

[Guest skyhacker]

Spotted another possible bug, Swype isn't working whenever´I try to select it as my main keyboard it forces close, anybody else has that problem ??

Edited February 15, 2011 by skyhacker

[Guest Victor von Zeppelin]

Problem is that the light sensor is mis-calibrated. Maybe it was posted here, maybe in the build topic, but in the CM7 settings/Display/Auto light sensor menu you can set the light sensor's settings, and all value was given. After that fix, after-call UI will work properly.

EDIT

Found it, it is in this very topic, comment #918 by Victor von Zeppelin!

Hey, No problems guys. I didn't actually know I had fixed this. It was just inadvertently fixed via playing with the settings. Haha, lucky guess, I 'spose.