Hey guys I'm using this nightly but most of the apps that I bought aren't compatible anymore. How can I change this? I heard something about LCD density?
Sorry... I'm still pretty new to this... how do I go about doing that?
Thanks.
That fixed it! thanks.
Weird though, ES file explorer was freezing up for a while, and the build.prop file sometimes took forever to load.
EVERYTHING works except camera, which is on the way! Arjen fixed, but lupo has problems, so it is almost full-featured! Wtf does not work? Give me the list and I will prove you're wrong
Anyone else had problems with the funny SIM flashable zip? It worked on mine but I'm not sure if I signed it properly...
Sent from my LG Optimus One by carrier pidgeon
...Anyone else had problems with the funny SIM flashable zip? It worked on mine but I'm not sure if I signed it properly...
Sent from my LG Optimus One by carrier pidgeon
HAHA I got excited and clicked the link hoping to see some magic fix... was my own post lol
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: