Actually, this new nightly is the same as adfad's earlier build.
No changes whatsoever..
Sent from my LG-P500 using Tapatalk 2
maybe 2-3 changes specific to gingerbread branch, because adam's KANG was build on 16 April and this one is on 21 April
EDIT:Mic with headphone fix is also in nightlies but might not be in KANG
I use rc1 with 480/729 , conservative. Camera flickering appears only with interactive governor. I know because i tested all governors.
Sent from my LG-P500 using XDA
I've been following it and nothing's changed,, just go to r.cyanogenmod.com to see it..
Sent from my LG-P500 using Tapatalk 2
In last nightly persist the proximity sensor's bug. It appears on some p500 only with cm stock kernel, with others, like roq or ta, doesn't appears.
Adam's March Kang had a better Camera... I am using OnDemand 748 MHZ. While on March KANG, there was no flicker in camera... But now, there is flicker...
adfad666 said:Feel free to talk about anything related to these ROMS, but to receive acknowledgement 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
Hey guy's, first post but lots of lurking!! I can't get mobile data (3g) to work with this or any other cm roms. It does work on stock 2.3.3 V20a.I see a new BB fix posted here, I am currently on this rom and would like to try it, do i just reboot into recovery-install zip and reboot? Thanks and i'm sorry if i posted this wrong!
i can't tether my phone 3g network over usb... using rc1 with franco kernel 4.. any one can help?
Sent from my LG-P500 using xda premium
i can't tether my phone 3g network over usb... using rc1 with franco kernel 4.. any one can help?
Sent from my LG-P500 using xda premium
Adam's March Kang had a better Camera... I am using OnDemand 748 MHZ. While on March KANG, there was no flicker in camera... But now, there is flicker...
Hey guy's, first post but lots of lurking!! I can't get mobile data (3g) to work with this or any other cm roms. It does work on stock 2.3.3 V20a.I see a new BB fix posted here, I am currently on this rom and would like to try it, do i just reboot into recovery-install zip and reboot? Thanks and i'm sorry if i posted this wrong!
In last nightly persist the proximity sensor's bug. It appears on some p500 only with cm stock kernel, with others, like roq or ta, doesn't appears.
I have checked it but i think this isn't the problem, because also in "proximity sensor finder " app doesn't work. So the solution posted here: http://xdaforums.com/showpost.php?p=22767195&postcount=2708 could help to fix this problem.Make sure you checked Settings > Call settings > Always use proximity.
If you still have problems after that, don't hesitate to report it again.
I have checked it but i think this isn't the problem, because also in "proximity sensor finder " app doesn't work. So the solution posted here: http://xdaforums.com/showpost.php?p=22767195&postcount=2708 could help to fix this problem.
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: