Lots of open GB changes merged to git repository today, hoping for next nightly in a day or two....
Last edited:
Lots of open GB changes merged to git repository today, hoping for next nightly in a day or two....
Thanks myawan!
Here you can see it better:
http://review.cyanogenmod.com/#q,status:merged+branch:gingerbread,n,z
sorry for quotingHey 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:
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..
sorry for quoting
---------- 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
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
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]
.................+1Well, 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.
Still reboot on incoming calls sometime 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.
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
So it is bcoz of franco kernel which i m using
Sent from my LG-P500 using xda premium
If I understand it correctly,
night·ly /ˈnaɪtli/
adj.
- Of or pertaining to the night, or to every night; happening or done by night, or every night.
- A Fresh CyanogenMod ROM automatically built with the newest available code, usually compiled at night. Often contains many bugs.
I noticed its difficult to get the pop-up menu when I hold the power button down.
I'm getting an error when trying to turn wi-fi on after flashing the testing kernel and the last nightly.
With screen on animation there are white noise before animation and when receive a call, need some time before i can answer.
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: