Post Your CyanogenMod 7.2 Nightly Questions HERE!!

Search This thread

Umang96

Inactive Recognized Developer / Themer
Oct 1, 2011
2,757
9,683
New Delhi
Hey guys, I've been having troubles with CM7.2 RC1 on my OG Droid. The autobrightness just doesn't seem to want to work.

I know my light sensor is working fine. I checked it in Z-DeviceTester.

When set to Auto Brightness, it is just always on the very brightest setting. Also, the softkeys and keyboard backlights don't turn on at all unless I manually change the brightness. Even then, after locking and unlocking the phone, they turn off until I change the brightness again.

I'm not seeing any solutions anywhere I've looked. Does anyone have any suggestions as to how to fix this issue? I'm really loving this ROM except for this one issue.

I've tried reflashing the ROM, wiping the Dalvik cache, but I haven't done a full data and cache wipe.

EDIT: I just realized this is in the wrong thread. I'm sorry! I'm obviously a noob, so I don't know how to delete it or move it to the correct thread. I'm just so helpless! D:
sorry for quoting :p

---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------

New bugs discovere are-
1.)white noise on unlocking screen.
2.)bad baseband version in about phone
3.)Flickering statusbar icons, when using battery percentage.
Note- the problems 1 & 2 are kernel bugs..
 
Last edited:

NeuDLi

Senior Member
Feb 11, 2011
200
425
New bugs discovere are-
1.)white noise on unlocking screen.
2.)bad baseband version in about phone
3.)Flickering statusbar icons, when using battery percentage.
Note- the problems 1 & 2 are kernel bugs..

White noise is known to be a side-effect of the fix for the reboot on calls. No big deal anyway, I would not even call it a bug, but rather a small glitch. Same for point 3.

What makes you think point 2 is kernel-related? See here, it is apparently not kernel-related as the already proposed fix does not change the kernel sources:

http://review.cyanogenmod.com/#change,13669
 

danielcr12

Senior Member
Apr 24, 2009
423
56
Nueva Esparta
danielcr.com
sorry for quoting :p

---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------

New bugs discovere are-
1.)white noise on unlocking screen.
2.)bad baseband version in about phone
3.)Flickering statusbar icons, when using battery percentage.
Note- the problems 1 & 2 are kernel bugs..


1&2 i am using cm7 stock kernel i dont have this bugs ( in fact i have used lot of kernels never had those bugs) ans 3 this is theme related, i use ICS theme and it doesnt have this flickering
 

nok2626

Member
May 14, 2011
44
9
I was using CM7.2 RC1 for about a week. The bug I have is the in-call volume is very low even though I set the volume to max during the call.
Next I flashed Oxygen ROM 2.6. There too I had the same problem.
Next I restored my stock ROM from my backup and I don't find the volume bug.

[Edit] Forgot to mention. The above bug happens only when I use the earphone. [that came with mobile]

Could you help me out here.

Is there any way LG's FM radio app could work in CM7. [I already tried Spirit FM]
 
Last edited:

petru.tomsa

Senior Member
Feb 2, 2012
596
85
Bugs:
1. If the phone is put to charge and to ring in the morning the hour will not update in standy and so will not ring.
2. The batery go faster discharge
3. Radio not working
4. I dont like setting menu is same color title with description (ex. Bluetooth- activate bluetooth) and also not have icons.
5. Not have posibility to find contact from right side the a,b,c... or up search bar you most enter in search menu.

But phone is moving nice but with go launcher ex not with adw launcher.

Hope will be a stable version better .:confused:

Sent from my LG-E510 using Tapatalk 2 Beta-2
 

mrbenbiz

Senior Member
Feb 15, 2011
240
103
Samsung's Galaxy
I was using CM7.2 RC1 for about a week. The bug I have is the in-call volume is very low even though I set the volume to max during the call.
Next I flashed Oxygen ROM 2.6. There too I had the same problem.
Next I restored my stock ROM from my backup and I don't find the volume bug.

Could you help me out here.

Is there any way LG's FM radio app could work in CM7. [I already tried Spirit FM]

Well, i think that nok2626 is right somehow. I've also noticed some volume bug in/during call. Sometimes volume is louder while i set it to minimum, or very low volume while was set almost to maximum. This is random to me, sometimes is working well.
Also there is a ringtone bug, i think someone else reported too, if i set an mp3 ringtone no matter that the mp3 is on /system/media/ringtones or on SDCARD, the ringtone don't loop forever, it's stops as soon the song is finished.
 
Last edited:

ravidahiya74

Senior Member
Nov 4, 2011
73
7
Well, i think that nok2626 is right somehow. I've also noticed some volume bug in/during call. Sometimes volume is louder while i set it to minimum, or very low volume while was set almost to maximum. This is random to me, sometimes is working well.
Also there is a ringtone bug, i think someone else reported too, if i set an mp3 ringtone no matter that the mp3 is on /system/media/ringtones or on SDCARD, the ringtone don't loop forever, it's stops as soon the song is finished.
.................+1
 

haxor

Senior Member
Apr 14, 2011
1,917
1,202
some where
Still reboot on incoming calls sometime :confused: lets hope will be fix in next release :)

Sent from my LG-P500 using xda premium
 

yuripg1

Senior Member
Oct 9, 2011
288
199
33
Canoas, Brazil
Still reboot on incoming calls sometime :confused: lets hope will be fix in next release :)

Sent from my LG-P500 using xda premium

Man, you're not using the stock kernel. That's why you're experiencing this bug.

Franco.kernel #4 is based on the code of CyanogenMod kernel BEFORE the problem of reboot on incoming calls (and other waking situations) was fixed.

CyanogenMod kernel included in RC1 has fixed this.
 

haxor

Senior Member
Apr 14, 2011
1,917
1,202
some where
Man, you're not using the stock kernel. That's why you're experiencing this bug.

Franco.kernel #4 is based on the code of CyanogenMod kernel BEFORE the problem of reboot on incoming calls (and other waking situations) was fixed.

CyanogenMod kernel included in RC1 has fixed this.

So it is bcoz of franco kernel which i m using :confused:

Sent from my LG-P500 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 76
    Добро пожаловать, друзья! Welcome, Friends! आपका स्वागत है, दोस्तों! Benvenuti, amici!
    Bem-vindos, amigos! Ласкаво просимо, друзі! Bine ati venit, prieteni! 欢迎 朋友们
    Vítejte, přátelé! chào đón, bạn bè! Willkommen, Freunde! Bienvenidos, amigos!


    in7kew.jpg


    The latest CyanogenMod Nightly can be downloaded here or via ROMManager.
    The new recovery in ROMManager (5.0.2.7) is not required, but is necessary to receive automatic updates.

    Changelog
    [I'm not going to provide my own changelog as all updates to CM7.2 are minor bugfixes only...]

    Other necessary files: Google Apps (Also available in ROMManager)

    night·ly /ˈnaɪtli/
    adj.
    1. Of or pertaining to the night, or to every night; happening or done by night, or every night.
    2. A Fresh CyanogenMod ROM automatically built with the newest available code, usually compiled at night. Often contains many bugs.

    This is the place to discuss the CyanogenMod nightlies. Feel free to talk about anything related to these ROMS, but to receive acknowledgement by a developer of any problems you find, the following conditions should be met:
    • Use the stock CyanogenMod kernel
    • Do not overclock
    • Use the default system apps (launcher etc.)
    • Do not use apps2sd or similar
    Before posting a problem you should:
    • Check the posts below for a solution / fix
    • Read the last 10 pages of this thread for a post with a similar problem
    • Backup, reflash with a full wipe, check if the bug is still there
    • Wait 24 hours for the next nightly, the devs probably already know about it
    If the problem still persists after the next nighlty appears and all the above steps have been followed, post your problem and we'll see if there is something we can do. Please include the following information:
    • Which Nightly you are running
    • Which Nightly the bug first appeared (if known)
    • *Confirm Stock Everything* (shows that you have read all the above)
    • Detailed steps to reproduce the bug (add a screenshot if it helps)

    OLD BASEBAND?

    If your phone uses the old baseband, you need to upgrade to the new baseband. This improves 3G signal and battery life. There are many guides on how to do this so just have a quick look around, or even watch a video on Youtube.

    NO-APN PROBLEMS?

    All APN problems related to 'funny SIMs' have been fixed, please thank werewolfo for generously donating an Italian funny SIM for me to test with!.
    28
    Major improvements include:
    • New baseband support
    • Better 3G Reception
    • .35 kernel support (only)
    • Offline charging
    • Quicker GPS lock
    • Smoother Accelerometers
    • Better 3G signal
    • Better battery life
    • CyanogenMod Updates
    24
    I noticed its difficult to get the pop-up menu when I hold the power button down.

    Hold the power button down until you feel it vibrate twice.

    I'm getting an error when trying to turn wi-fi on after flashing the testing kernel and the last nightly.

    The test kernel is a kernel only, none of the other included files came with it. If you flashed another kernel it won't work.

    With screen on animation there are white noise before animation and when receive a call, need some time before i can answer.

    You shouldn't really be enabling screen on animation, it's always been buggy for msm7x27 chips which is why it's disabled by default. But if it works, static is a small price to pay for a phone that doesn't reboot on an incoming call...

    PS here's a KANG that includes the fixed kernel and fixed camera...

    http://www.mediafire.com/?p0di9g79ck80a0c
    19
    Ok. As you know, init is the first process after kernel started. Init parse /init.rc and /init.[device_name].rc and execute early-init action in it. Ueventd is one of the very first services started by the default init.rc. It proceeds to read its main configuration files, /ueventd.rc and /ueventd.[device_name].rc, replays all kernel uevents (i.e. hotplug events), and then proceeds on to wait, listening for all future uevents. Kernel uevents are delivered to ueventd through a netlink socket, a common way for certain kernel functionality to communicate with user-space tools and daemons. [device_name] we get from "androidboot.hardware" kernel commad line - in our case it "thunderg" (look BoardConfig.mk). In early builds we got file /uevent.thunder.rc , after typo fix we have /uevent.thunderg.rc and have problem with /dev permissions - ril, sensor, gpu not work. Download latest nightly, flash, then apply patch in attachment - and manual network selection was work :fingers-crossed:
    18
    Finally audio with headphones is fixed!

    I spent ages looking for a way to enable the microphone with stereo output, then I realized I can just detect if we are in a call or not and swich to mono with working mic :rolleyes:

    http://review.cyanogenmod.com/#/c/14710/

    EDIT: here is an unofficial build to play with

    http://www.mediafire.com/?4b933wa09351rjv

    changelog: 'stuff' is fixed ;)