CM7 Nightly Discussion Thread [Old, please use new thread]

[Guest Swimmerboy]

Is gapps included?

How do I go about Installing this?

*The vital first step is download either Tom's or Seb404's ClockworkMod. Seb's is here, with instructions

*Next is to do a Nandroid backup within Clockwork. This will produce a full backup of your current ROM, so you can go back to it at will.

*Wipe data/ do a factory reset

*Install the ROM .zip file.

*Install Google Apps, which are HERE

*Restore and backup, install new apps

*MOVE ANGRY BIRDS TO THE PHONE. As this is the most common complaint, please move troubling programs to the phone.

(Although the link seems to be broken to gapps)

Edited March 4, 2011 by Swimmerboy

[Guest birdibird]

Is gapps included?

gapps is included, it wil give you a screen to select the gapps after which it will download them from the market.

no need to seperately flash gapps anymore from N11

[Guest The Soup Thief]

gapps is included, it wil give you a screen to select the gapps after which it will download them from the market.

no need to seperately flash gapps anymore from N11

Alternatively don't bother - if you click No on that screen but have previously had those apps on your phone from the market, they will automagically download from the market later - make sure you have both boxes ticked in Privacy (Back up my data and Automagically restore - I'm not sure which of the two does the magic, but with both together it seems to work)

There's an interesting bit of background to this on the Wikipedia page for Cyanogenmod, explaining how the Google initially got moody with CM for including google apps, and though they later chilled out a bit, Cyanogenmod firmware has since played safe of the copyright laws by not bundling google apps with the firmware

[Guest Victor von Zeppelin]

(Although the link seems to be broken to gapps)

Works perfectly for me. Direct link 'an all. But as already has been said, it doesn't matter, Gapps are in.

[Guest The Soup Thief]

I've just been playing with lockscreen gestures in cyanogenmod options - VERY cool!

Likely most will have seen these already, but I've only just found them - if you don't know about them, Home>settings>Cyanogenmod settings>Lockscreen> [there's something good in most everyone of these options, but Lockscreen gestures has impressed me most]

Custom app slider in style options is very swanky too :(

[Guest tnat]

Is gapps included?

Gapps never will be included with CM. But downloadable.

Edited March 4, 2011 by tnat

[Guest tutu101]

I tried CM7 for the first time on my Orange San Francisco (TFT) using Nightly 12.

My thoughts (I have read the thread also.):

Launcher is very choppy (will have to search the thread to turn off those lines) - I downloaded ModaCo Launcher and used that but it didn't replace the home screen (I am new to this)

Got random screen freezes (had to press power button to get the screen back on)

Unable to sync my contacts with gmail (I did install google apps)

Angry birds runs quite well (on phone)!!

I can't find task manager??

Car Home doesn't run (I did try re-installing from market?)

Too early to say for battery usage.

[Guest forney27]

I've just been playing with lockscreen gestures in cyanogenmod options - VERY cool!

Likely most will have seen these already, but I've only just found them - if you don't know about them, Home>settings>Cyanogenmod settings>Lockscreen> [there's something good in most everyone of these options, but Lockscreen gestures has impressed me most]

Custom app slider in style options is very swanky too :(

thanks for the tip, there are quite a few cool features and this is one ive not used....very cool indeed

Too, as far as battery life (and not to beat a dead horse) by turning my brightness down, it seems by battery life has doubled...

[Guest _amano]

--

Edited March 4, 2011 by _amano

[Guest Watashi_PT]

how can i fix the black screen after a call? i think i read it somewhere in this post.

that is the only thing that bother me because i use the phone to call very much.

[Guest tttonyyy]

Every call I've made today has left me with the screen off and no way to terminate the call without popping the battery out; it's annoying enough to make me want to move back to a 2.2 ROM until it's fixed. I'm on N12.

[Guest marcodassi]

Funny how many people still complains about blank screen / battery life / etc. on a NIGHTLY BETA firmware...

You have to use the phone all the day for voice calls? Keep the standard ROM so!

OR... as I've said before at least 2-3 times... use a BLUETOOTH HEADSET!

cheers

marco

PS I don't want to be offensive, but I get really annoyed at all those complains on a FREE product...

Edited March 4, 2011 by marcodassi

[Guest The Soup Thief]

Every call I've made today has left me with the screen off and no way to terminate the call without popping the battery out; it's annoying enough to make me want to move back to a 2.2 ROM until it's fixed. I'm on N12.

Hi tttonyyy

Try these ideas (each kinda works for me by way of a temporary workaround)

1. when you take the phone from your ear and it doesn't wake, put your thumb over the proximity sensor for 5 seconds then uncover it. Try it again if it doesn't work first time

2. install JustShake Free from the market and set this to jiggle awake. I'd give you better directions but it's just started force closing on me for some reason! Reinstalling it...

3. Am sure i found a way of ending calls and waking the screen with the power button in the cyanogenmod options ealier - can't find hide nor hair now - will repost if it turns up

That wasn't as helpful as i'd hoped, but try number 1 - works for me every time

[Guest Maz2011]

Every call I've made today has left me with the screen off and no way to terminate the call without popping the battery out; it's annoying enough to make me want to move back to a 2.2 ROM until it's fixed. I'm on N12.

Pushing the on/off button a few times brings the screen back for me and AFAIK the first push on the button cuts off the call. I never call out anyway so I'm not too bothered!

This, the screen freezing and the poor battery life do seem to be extremely basic faults though and I'm a bit surprised that more attention isnt being paid to them instead of some other exotic features that most people will probably never use. Not that I'm complaining at all: there is no doubt that the phone works far better with this than with the default Orange firmware.

A Bluetooth headset may be OK for some but I carry my phone in my shorts pocket and have no room for other bits and pieces.

[Guest wbaw]

Every call I've made today has left me with the screen off and no way to terminate the call without popping the battery out; it's annoying enough to make me want to move back to a 2.2 ROM until it's fixed. I'm on N12.

Putting my thumb over the proximity sensor works for me. It seems to work randomly.

[Guest Krinyo]

Funny how many people still complains about blank screen / battery life / etc. on a NIGHTLY BETA firmware...

Not so funny, if You read this on the first page of this topic:

[FIXED]Proximity Sensor

So it's not fixed. :(

[Guest Grain]

Not so funny, if You read this on the first page of this topic:

[FIXED]Proximity Sensor

So it's not fixed. :(

What do you expect? Victor is not omniscient and can only assemble the information people provide here. Then again, since many people drop partial information and sometimes just outright wrong stuff ("battery drain SOLVED!!1!!" when having tested for 10 minutes etc. :( ), there's nothing he can do really about that. Plus the fact that the nightlies are a moving target does not help.

Plus, of course, the fact that forums are really not suited for managing actual information. The first post should be a wiki page really. Then other people could also fix it.

[Guest _amano]

http://r.cyanogenmod.com/#change,3574

Cyanogen himself added some camera stuff today. This might help with the 5 MP issues und the issues with the wrongly saturated colors.

And it is probably the patch that Tom G was waiting for (his own camera patch waits for the final "OK" for 2 weeks now).

All 5MP users, please test the upcoming nightly 13

@Victor:

*Looking at the official proximity bug report, Tom G stated that he was working towards a more comprehensive fix and that the current one was just a workaround that didn't cover ALL usecases. Thus I would change [FIXED]Proximity Sensor --> [iMPROVED] Temporary proximity sensor workaround

*Spelling error: "Also, take a peek at the General CyanogenMod cahngelog to see ..."

*Remove from the broken issues: "Data connection established when turning wifi off"

Perhaps add: "Still some remaining proximity sensor usecases left (just partially fixed)"

Edited March 4, 2011 by _amano

[Guest simonckenyon]

i had the problem with the screen not coming back on

but now i don't.

i'm using #12.

when i started to have the problem i made a few of the changes that were suggested on the various forums.

i do not have any special software installed.

so maybe there is some combination of settings which solves the problem.

[Guest The Soup Thief]

Putting my thumb over the proximity sensor works for me. It seems to work randomly.

Ok - I've just made about a dozen calls to voicemail, checking the screen reakening each time

After the first couple I cocked up the fairly good success I was having with covering and uncovering the proximity sensor

:D

But I persevered

Currently I have the following in Call Settings

Keep Screen awake (tick)

Always use proximity (tick)

Always back to call log (tick)

Incall touch UI (untick)

Everything else unticked (don't think they matter too much)

Rats!

It worked for a bit, but then stopped. It seems that if you go in and untick and then tick Keep screen awake, it will work for the next call, but then it goes all wanky again

Important one though to make this livable with, so your screen doesn't blank mid call leaving your call ongoing and requiring a battery pull to disconnect - Setting>Accessibility>Power button ends calls

All you'll need to do is hit the power button to end the call then you can tit about covering and uncovering the sensor for a while til it responds. I've just managed to do something to make mine loads less reponsive but I've no clue what

I was messing about with the light sensor settings in CM settings but I dunno what I dun!

Important to set display time out to a couple of minutes or more - if it times out while the screen's still blank you'll have to pull the battery

Maybe a breakthrough?

Can someone else try and replicate this...

Ignore all of the above and in Display Settings go to Animation and pull down to All windows animations are shown

And that seems to be it!

Just changing that has got mine reawakening either automatically or with only a quick brush of the thumb over the sensor!

:( :( :) ;) No idea why ;) :D :D

[Guest Watashi_PT]

i had the problem with the screen not coming back on

but now i don't.

i'm using #12.

when i started to have the problem i made a few of the changes that were suggested on the various forums.

i do not have any special software installed.

so maybe there is some combination of settings which solves the problem.

tell me please what you did

[Guest tttonyyy]

Hi tttonyyy

Try these ideas (each kinda works for me by way of a temporary workaround)

1. when you take the phone from your ear and it doesn't wake, put your thumb over the proximity sensor for 5 seconds then uncover it. Try it again if it doesn't work first time

2. install JustShake Free from the market and set this to jiggle awake. I'd give you better directions but it's just started force closing on me for some reason! Reinstalling it...

3. Am sure i found a way of ending calls and waking the screen with the power button in the cyanogenmod options ealier - can't find hide nor hair now - will repost if it turns up

That wasn't as helpful as i'd hoped, but try number 1 - works for me every time

I've experimented with calling my desk phone, and the thumb 5 seconds over the proximity sensor does indeed work (I'd tried briefly covering and uncovering it before but clearly not long enough).

Also shaking works but I seem to have to give it a bloody good shake to terminate the call (more so than when just testing the shake function in the menus for some reason).

I'd just downloaded JJ9 and was about to flash it when I read your post, so many thanks for taking the time to reply :(

[Guest The Soup Thief]

I've experimented with calling my desk phone, and the thumb 5 seconds over the proximity sensor does indeed work (I'd tried briefly covering and uncovering it before but clearly not long enough).

Also shaking works but I seem to have to give it a bloody good shake to terminate the call (more so than when just testing the shake function in the menus for some reason).

I'd just downloaded JJ9 and was about to flash it when I read your post, so many thanks for taking the time to reply :(

tttonyyy - what do you have Settings>Display>Animation set to?

My guess is "All window animations are shown".... (if that worked for you)

[Guest tttonyyy]

Important one though to make this livable with, so your screen doesn't blank mid call leaving your call ongoing and requiring a battery pull to disconnect - Setting>Accessibility>Power button ends calls

Ahha! Genius - that's just what I need, just tried it out and it hangs up every time :(

Do still need to stick a thumb over the sensor to get the screen back afterwards, but that'll do nicely for now!

Edited March 4, 2011 by tttonyyy

[Guest richardkemp]

I have never had any problem whatsoever with the blank screen after calls since it was reported fixed. For the record I have always had animations set to 'all', though I don't see why that would make a difference.