[DEV][ROM] CyanogenMod 7.2.0 (Android 2.3.7)

[ccav2000]

It vibrates in each setting - never, always, in silent mode, etc. - does not matter.
It my opinion it should be quiet when in a silent mode.
yeah we are talking about 08-22.
Maybe next nigtly (keira) will work fine.

Keep up the good work devs - I hope you know devs how many people got great phone because of you!

Just tested trying to reproduce this, I can't. Vibrate set to never, Silent mode selected, the phone stays silent and no vibration.
Running the cm7-110901-1516-NIGHTLY

 

[m_zet]

Just tested trying to reproduce this, I can't. Vibrate set to never, Silent mode selected, the phone stays silent and no vibration.
Running the cm7-110901-1516-NIGHTLY

Still the same in 0901 nightly - vibrates when in silent mode.
After installing I did cache/dalvik wipe.

Is there any other place where sound is set?

edit:
Just went back to 2011-07-29 and in silent mode no vibration.
So something is not right in 08-22 and 09-01 with vibration - because it vibrates in any mode.

edit2:
What is really strange - why in 2011-07-29 there is no such problem and in 2011-08-22 and 2011-09-01 it is.?
This is the same situation when I read about wifi problems - I got no such problem. But is does not mean that the problem is not there - so many ppl wrote about it in the past.
So anyone else having the same issue here?

 

[hailmary]

Still the same in 0901 nightly - vibrates when in silent mode.
After installing I did cache/dalvik wipe.

Is there any other place where sound is set?

edit:
Just went back to 2011-07-29 and in silent mode no vibration.
So someting is not right in 08-22 and 09-01 with vibration - because it vibrates in any mode.

tried to reproduce this issue here.im on the latest knightly 110901-1516..
phone dont vibrate in silent mode on mine.all is just fine.

 

[Kiristiba]

tried to reproduce this issue here.im on the latest knightly 110901-1516..
phone dont vibrate in silent mode on mine.all is just fine.

+1

greetings

 

[chab7]

@SeiferTV
I'm on the very latest nightly (cm7-110901-1516-NIGHTLY) and all works perfectly.
I got there by first installing cm7-110822-1650-BOOT179-4 and then the nightly on top. But I don't think only installing the latest nightly will make a difference. You'll be then on the BOOT179 kernel and not BOOT179-4.

Here's how I install the nightlies and didn't have any issues so far.

Boot into 2ndInit -> Recovery -> Stable recovery (simply press power button -> reboot -> recovery)
Select "Wipe cache"
Go to "Advanced"
Select "Wipe dalvik cache"
Select "Wipe battery stats" (you don't need to do this for every nightly you install)
"+++++Go Back+++++", then select "Install zip from sdcard", "choose zip from sdcard", then select nightly zip
Select "choose zip from sdcard", then select gapps
Select "+++++Go Back+++++", then "reboot your system now"

The link to the nightlies and gapps are on the first page of this thread. I also recommend you install the latest google apps (gapps-gb-20110828-signed.zip) as well.

This method is almost the perfect. I must correct 2 points. If gapps is installed than need install next only when new gapps update is out.
Before you press "reboot your system now" at the end make a "wipe cache" and "wipe dalvik" again, to keep some local bugs off. (I had FM RDS problem from nightly to nightly what was not rom bug but local bug and wipe cache after install zip eliminated it)

 

[mick711]

Git problem ?

Hello

Very strange i reset all , delete files and folder make a new install of repo but i have this problem when i compile :

build/core/base_rules.mk:479: attention : écrasement des commandes pour la cible « out/target/product/jordan/system/bin/charge_only_mode »
build/core/base_rules.mk:479: attention : anciennes commandes ignorées pour la cible « out/target/product/jordan/system/bin/charge_only_mode »
build/core/notice_files.mk:50: attention : écrasement des commandes pour la cible « out/target/product/jordan/obj/NOTICE_FILES/src//system/bin/charge_only_mode.txt »
build/core/notice_files.mk:50: attention : anciennes commandes ignorées pour la cible « out/target/product/jordan/obj/NOTICE_FILES/src//system/bin/charge_only_mode.txt »
build/core/dynamic_binary.mk:118: attention : écrasement des commandes pour la cible « out/target/product/jordan/symbols/system/bin/charge_only_mode »
build/core/dynamic_binary.mk:118: attention : anciennes commandes ignorées pour la cible « out/target/product/jordan/symbols/system/bin/charge_only_mode »

What files or parameters is bad on the GIT ?

Thanks if you can help me because all of my new compile won't boot .

 

[henel321]

Wifi tethering works well in 20110901 as well... Very happy camper indeed!

Sent from my Transformer using Tapatalk, tethered using wifi on Defy, listening to music using a BT-headset... Wireless FTW!

 

[Zerobarat1]

Hey guys, I tried a while back 179-04 and WI-FI didn't work. Did the latest nightlies bring anything to the table regarding this issue? Currently I'm on 179-02 with the latest nightly applied over it.
Thx in advance

 

[m_zet]

Hey guys, I tried a while back 179-04 and WI-FI didn't work. Did the latest nightlies bring anything to the table regarding this issue? Currently I'm on 179-02 with the latest nightly applied over it.
Thx in advance

I am one of many for whom wifi works well in each build - rc1, rc1 v2, nightlies etc.

 

[zakoo2]

I am one of many for whom wifi works well in each build - rc1, rc1 v2, nightlies etc.

no, i never had any wifi problems (only when i couldnt set the regulatory domain, my router was set to 12 channels, while my phone to 11, so it didnt find the network). i only had issues with gsm and gps. and now with battery drain :/ btw, i noticed a bug: when i disable lockscreen and enable screen-on animation and listen to music, the screen wakes up when trying to skip/pause a song with the headset button. can anybody reproduce this bug? (110830 nightly, playerpro)

sent from my cm7 defy...

 

[malteof]

Please everyone in this thread, support Quarx et al in their great effort! Buy "Donate for Defy CM7" right away.

If you use CM7 on your Defy, $5 is nothing. Keep up the great work.

Sent from my MB525 using xda premium

 

[mick711]

I am one of many for whom wifi works well in each build - rc1, rc1 v2, nightlies etc.

Wifi problem is when you have WPA2 not with WPA or WEP

 

[iammodo]

Please everyone in this thread, support Quarx et al in their great effort! Buy "Donate for Defy CM7" right away.

If you use CM7 on your Defy, $5 is nothing. Keep up the great work.

Sent from my MB525 using xda premium

If you need a google music invite I said I would invite anyone who has a screenshot of their phone with the cm7 app just pm me your email.

 

[ankit_harry1992]

hey,
how can i know my current boot version??( m on stock froyo)

also, looking to flash cm7, so shud i fst flash boot179 nightly nd then the latest nightly to avoid any wifi probs or directly the latest nightly??

and what if i want to go back to my older boot, then wud i have to start all over again by flashing stock froyo fst??

lastly, while updating nightly, do we need to flash gapps again or not??

 

[Zerobarat1]

If you need a google music invite I said I would invite anyone who has a screenshot of their phone with the cm7 app just pm me your email.

If you help me out with WI-FI on 179-04 kernel sure I'll buy the support app right now, plus another device at a later date, either way I'll still buy the support app but at a later date if you cannot provide the assistance . If you have the time PM me cheers.

 

[remuseu]

hey,
how can i know my current boot version??( m on stock froyo)

also, looking to flash cm7, so shud i fst flash boot179 nightly nd then the latest nightly to avoid any wifi probs or directly the latest nightly??

and what if i want to go back to my older boot, then wud i have to start all over again by flashing stock froyo fst??

lastly, while updating nightly, do we need to flash gapps again or not??

it has been said many times...the boot nightly`s replace your kernel and the normal nightly`s dont
so the smart thing to do is to instal the latest boot (179-4 in this case) and after that the latest nightly (10901 in this case)

 

[EdwardN]

Difference between 179 and 179-4?

I'm sure it's been asked and answered before, and I apologise in advance for re-asking, but after reading through quite a bit of this thread I didn't find it. What exactly is the difference between boot 179 and 179-4? Is one preferable for red/green lens? I have a green lens Defy from Tmobile.

 

[twa_priv]

BOOT179: kernel from 3.4.2_179-2 CEE
BOOT179-4: kernel from 3.4.2_179-4 Vodafone Spain

I have tried both on red and green lense defy's and didn't notice any difference.
Currently I am on boot179-4, simply because it's the last boot nightly.

If you have issues with either one you can simply re-install the boot nightly you want followed by the non-boot nightly of your choice.

 

[mick711]

GIT Problem !

Hello

Impossible to download repo GIT is out or have a big problem :

[email protected]:~$ repo sync
android.git.kernel.org[0: 199.6.1.173]: errno=Connection refused
android.git.kernel.org[0: 130.239.17.13]: errno=Connection refused
android.git.kernel.org[0: 2001:6b0:e:4017:1972:112:1:0]: errno=Network is unreachable
android.git.kernel.org[0: 2001:500:60:10:1972:112:1:0]: errno=Network is unreachable
fatal: unable to connect a socket (Network is unreachable)
error: Cannot fetch repo
[email protected]:~$

So impossible to see if last error i have with batterycharge and many other is ok now

 

[maniac103]

Hello

Impossible to download repo GIT is out or have a big problem :

[email protected]:~$ repo sync
android.git.kernel.org[0: 199.6.1.173]: errno=Connection refused
android.git.kernel.org[0: 130.239.17.13]: errno=Connection refused
android.git.kernel.org[0: 2001:6b0:e:4017:1972:112:1:0]: errno=Network is unreachable
android.git.kernel.org[0: 2001:500:60:10:1972:112:1:0]: errno=Network is unreachable
fatal: unable to connect a socket (Network is unreachable)
error: Cannot fetch repo
[email protected]:~$

So impossible to see if last error i have with batterycharge and many other is ok now

Yes, the AOSP repo is out of order. Workaround: change git://android.git.kernel.org to http://android.git.kernel.org in .repo/manifest.xml.

Sent from my MB525 using Tapatalk