Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
making some much needed time tonight to begin on an update..
no eta's..might pump out a small update with updated apk's..and clean things up a little bit..sense most are out dated
Thanks Johnny keep up the awesome work I know I am not the only one who appreciates it.
Will be looking forward to the update, will it wipe all data? just wondering if I should backup to pc or not yet.
Will
Any luck this maybe ported to prevail. CyanogenMod 9 release candidate????
Found this here
Code:[B]Memory Allocation [/B] Android defaults to using two framebuffers for page flipping. in order to support this memory for the video subsystem needs to be allocate properly as part of the boot arguments: vram=32M omapfb.vram=0:16M these boot args allocate 32M for the video subsystem and then sets the display 0 to use 16M (half) for the primary portion of the display. For large screens (i.e. 1920x1200), it is necessary to double the amount of video memory: vram=64M omapfb.vram=0:32M If you have failed to allocate the memory properly you may receive one or more of the following errors: I/SurfaceFlinger( 1198): SurfaceFlinger is starting I/SurfaceFlinger( 1198): SurfaceFlinger's main thread ready to run. Initializing graphics H/W... E/SurfaceFlinger( 1198): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake E/FramebufferNativeWindow( 1198): couldn't open framebuffer HAL (Bad address) or I/SurfaceFlinger( 1198): SurfaceFlinger is starting I/SurfaceFlinger( 1198): SurfaceFlinger's main thread ready to run. Initializing graphics H/W... E/SurfaceFlinger( 1198): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake E/FramebufferNativeWindow( 1198): couldn't open framebuffer HAL (No such device) [B]Note:[/B] The above error messages could also be due to a mismatch in kernel/library versions of GFX drivers. Make sure they have the same version number. Refer to: [url=http://omapedia.org/wiki/Android_How-tos#Verify_Kernel_GFX_Version]Android How-tos - OMAPpedia[/url]

surface flinger was also an error that plauged the evo 4g build of cm9 and the developer building it figured out how to fix it..but he was also compiling nightlies and i dont have a build setup/enviorment..so i am sorrta handicapped at the moment because of the hardware im using..dualboot..garbage..i need a machine deicated to linux..so for now ill do what i can to help..which may not be much..but thank you for brining that up vince because i was just dealing with that issue and reading of it in the evo builds of cm9..most be a pretty common error for cm..i will pm jmz about it..hes the cm guy for the og evo
soooo nooo updates yet???? lol its been more then a month now![]()

Hey bro, delete some PM's So I can send ya one, lol...:smokingsomb:
oh yeah when someone gets a chance..could you just verify that 3g isnt broken..i dont have service on my prevail right now and cant test
...it has an unstoppable airplane mode. I try to reodin it stays in ap mode, ...and it still defaults to and stays in so mode.
I (or my phone) did this too! It was (I think) because I wrote a cricket prl to. I tried to check status and got fcs too. So I changed the prl back to the stock one 61007 in my area -Rockinham County, NC- and did a factory reset, rebooted and checked status successfully, and ##data#, ##debug#, and ##port# worked again without fc-ing. Hope this helps someone. And thanks for the m3id and 3sn solution. This could make sticky @ xda!
Hi new to the forums.I want to say love this mod so much and thanks for all y'all time and effort put into it.I have one problem with this mod,for some reason when I try to install app it downloads them and as soon as it begins to install the apps it reboots my phone and apps not installed.What am I doing wrong?
I did that and still have same problem should I wipe whole phone and reflash rom?