Is it just me or good old Andy's startup animation is gone in the latest build? Mine just boots with an LG logo.
Is it just me or good old Andy's startup animation is gone in the latest build? Mine just boots with an LG logo.
link guide http://xdaforums.com/showthread.php?t=2315341
ThanksJust flash the zip he provided.
Edit: By the way, you'll probably want to create a new thread in the Themes & Apps forum for your mods. It'll give you greater exposure.
Thanks!Yeah good idea. I can put a link in 2nd post to your thread. Keep it up with the mods x-dira
Sent from my Nexus 7 using xda app-developers app
link guide http://xdaforums.com/showthread.php?t=2315341
Thanks petrukgrinder
Thanks
Thanks!
Theme Ice9
http://www.mediafire.com/download/kuxury01e98kmlf/Ice9_mdpi_test26m7.apk
@Life'sGood; If you're looking for a good CM7.2 for the P500, I recommend using FitAmp's unofficial CM7.2 build rather than the official CM7.2. I believe the latest official nightly has some network issues, among others (though it's been a while since I used it, so I can't recall clearly), which have been fixed in FitAmp's build. If you're looking for a custom kernel to go with that, then DJNoXD's 2.5.8-ta-vsyncOff (or with vsync, your choice) kernel is the best option, IMHO (in fact, that's my current setup).
Regarding baseband, since you're on Froyo, then yeah, it's the old baseband. You can update to the new baseband if you want, but a safer option would be to simply flash the Old Baseband Fix right after flashing the ROM in order to restore network. The oldbb fix zip can be found in the 1st post of FitAmp's CM7.2 thread.
thanks for your answers. I'm planning to use the stable release instead of the nightlies that comes after it. Does it have any issues?
thanks for your answers. I'm planning to use the stable release instead of the nightlies that comes after it. Does it have any issues?
thanks for your answers. I'm planning to use the stable release instead of the nightlies that comes after it. Does it have any issues?
frameworks/base/services/camera/libcameraservice/CameraHardwareStub.cpp: In static member function 'static android::sp<android::CameraHardwareInterface> android::CameraHardwareStub::createInstance()':
frameworks/base/services/camera/libcameraservice/CameraHardwareStub.cpp:400: error: cannot allocate an object of abstract type 'android::CameraHardwareStub'
frameworks/base/services/camera/libcameraservice/CameraHardwareStub.h:31: note: because the following virtual functions are pure within 'android::CameraHardwareStub':
device/lge/e510/include/camera/CameraHardwareInterface.h:96: note: virtual android::status_t android::CameraHardwareInterface::getShutterSound(int)
device/lge/e510/include/camera/CameraHardwareInterface.h:142: note: virtual void android::CameraHardwareInterface::encodeData()
make: *** [out/target/product/e510/obj/STATIC_LIBRARIES/libcamerastub_intermediates/CameraHardwareStub.o] Error 1
make: *** Waiting for unfinished jobs....
external/yaffs2/yaffs2/utils/mkyaffs2image.c: In function 'mkyaffs2image':
system/core/include/private/android_filesystem_config.h:233: warning: inlining failed in call to 'fs_config': --param max-inline-insns-single limit reached
external/yaffs2/yaffs2/utils/mkyaffs2image.c:304: warning: called from here
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: