[ROM][OpenSource][Jun 12] Floyo 1.4pre1 Experimental (Stable Floyo 1.2.0)

Search This thread

kojitabe

Senior Member
Feb 15, 2011
207
27
Hi erasmux,

First,thanks for this stable rom,i use floyo 1.2.0.
I wanna try 1.4pre,but i wonder which kernel has the best battery life.
Because i'll i have a trip for a week,and i need the longest battery life so i don't need to charge everytime.

For next build,can i have cm setting to change cpu freq and governor?
And i wish i can have power widget button order too :D
But thanks anyway,it's a good,fast and stable rom.
 

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
1.4pre1 has the CPU speed and governor added to the CM Settings.
For maximum battery life, I recommend you update to the latest LasVenturax version as posted on the second post of the LasVenturas thread and use smartassV2.

Please note that I am currently actively developing both projects: a new kernel version should appear later today (with very small tweaks). A new 1.4pre version should appear later this week (I really hope).
 

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
Next problem.
Tried to copy a file ~100MB to SD card.
Device turns off SD card itself and then comes errors - device not ready, I/0 trouble etc. Several times.
Formated SD card, copied back to SD all files, same ****.
SD card - original.
Made a reboot to recovery, enabled USB-MS, copied all old files and new files - succesfuly.
1.4 + LVxf

That is very weird. For me this does not happened: I just copied 5x180M files to my SD card and the SD did not disconnect.
Does this also happened for you with FlyKernel? with LV 0.5.0? Assuming that it works for you at least with FlyKernel, try to generate a logcat and dmesg log for me, possibly there will be some clues there.

Anyone else also suffering from this?
 

kojitabe

Senior Member
Feb 15, 2011
207
27
1.4pre1 has the CPU speed and governor added to the CM Settings.
For maximum battery life, I recommend you update to the latest LasVenturax version as posted on the second post of the LasVenturas thread and use smartassV2.

Please note that I am currently actively developing both projects: a new kernel version should appear later today (with very small tweaks). A new 1.4pre version should appear later this week (I really hope).

Wow,thanks for your fast response.
Okay,i'll wait for new release,maybe i'll stick with 1.2.0 for now.
Love your works so much,thanks again for your enlightenment.
 

artursc

Senior Member
Jan 30, 2010
73
4
Riga
Here's a logcat.
Where can i find .txt file when i type adb logcat -d > logcat.txt ?

I made a new copy ~109MB .mp3 file and again same ****. I even changed USB cable several times, not cable problem.

I will try with FlyKernel now.
 

Attachments

  • logcat1_27aug.pdf
    31 KB · Views: 4
Last edited:

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
Here's a logcat.
Where can i find .txt file when i type adb logcat -d > logcat.txt ?

I made a new copy ~109MB .mp3 file and again same ****. I even changed USB cable several times, not cable problem.

I will try with FlyKernel now.

Wow a logcat in PDF format :D Still can't find any related errors there. Try to generate the full logcat (adb logcat > logcat.txt) and the dmesg log (adb shell dmesg > dmesg.txt).
Also verify that it works with FlyKernel, otherwise its not a kernel problem....
 

artursc

Senior Member
Jan 30, 2010
73
4
Riga
look at post upper
There are no problems with FlyKernel 12pre6

My best friend isn't computer, that's why i don't know where is that ****ing logcat .txt file ;)
 

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
look at post upper
There are no problems with FlyKernel 12pre6

My best friend isn't computer, that's why i don't know where is that ****ing logcat .txt file ;)

Simplest solution is:
start -> run -> "cmd"
if you wish change current directory
now:
adb logcat > logcat.txt
(logcat.txt will be in current directory :D)
and same for dmesg log just with the "adb shell dmesg > dmesg.txt" command.
 

artursc

Senior Member
Jan 30, 2010
73
4
Riga
No no,
i know how to adb make my aunt fly out of window etc.
but where is located file named logcat_made_today_for_one_fucking_problem.txt to send to this post??
 
  • Like
Reactions: timbohobbs

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
Las_Venturax-0.6.0.zip (multiupload)
  • Tweaked scheduler parameters (added HRTICK and lowered latency to minimum - ROM developers please do NOT overwrite the scheduler params in your init.rc)
  • Added smartassV2 governor as the new default governor - more details below (since 0.5f, tweaked built in sleep in 0.6.0)

I hope I don't eat my hat, labeling this release 0.6.0 as if it is somewhat stable. A more final 1.0 stable release will most likely be done by Riemer when he has time for this.

The main difference from the 0.5f version is that the scheduler parameters have been tweaked to an extreme. I have done such a change and lived to regret it (in the FlyKernel 12 release), but this time I have changed the parameters to the complete opposite direction which make more sense :D.
Seriously, I would like feedback, does the new version feel different than the previous 0.5f version mainly in terms of responsiveness.

On the way (actually this is what I sat out to do in the first place), I have hopefully fixed playing music during sleep @ smartassV2 with a minimum frequency of 176Mhz. The situation should at least be much better if not 101% fixed.

Feedback, which is more kernel related than ROM related would be better placed on the LasVenturas thread, but I'll read it even if you post it here :D.
 

DjoeN

Senior Member
Aug 10, 2010
680
145
Planet Earth
erasmux,

Is it possible to leave the new market app out and use the previous version?
I think the new market is to slow for the Hero.
 

JieeHD

Retired Recognized Developer
Dec 29, 2010
734
388
Glasgow
No no,
i know how to adb make my aunt fly out of window etc.
but where is located file named logcat_made_today_for_one_fucking_problem.txt to send to this post??

He already answered that, the logcat is stored in your SDK directory. There is no need to start on Eran when he is only trying to help you solve an issue, remember he doesn't need to help you at all or provide the ROMs and kernels he has. Bit more of a courteous attitude next time.

Sent from my HTC Hero using xda premium
 

lohtse

Senior Member
Apr 1, 2009
1,719
146
Where ever they send Me!!
He already answered that, the logcat is stored in your SDK directory. There is no need to start on Eran when he is only trying to help you solve an issue, remember he doesn't need to help you at all or provide the ROMs and kernels he has. Bit more of a courteous attitude next time.

Sent from my HTC Hero using xda premium

You beat me too it!!!!!

If memory serves me correct this was the cause of the developer leaving once before.... PLEASE be courteous as without these developers we would have a poor rom on our devices.With them we get the best are devices actually can be and are...


regards

lohtse
 

dkelley

Senior Member
May 11, 2010
2,957
190
Maple Ridge (close to Vancouver)
No no,
i know how to adb make my aunt fly out of window etc.
but where is located file named logcat_made_today_for_one_fucking_problem.txt to send to this post??

LMAO

this is one of the crankiest posts I've seen in a long time.

funny thing about logcats - if you make them using alogcat.apk on the phone itself, you know where it saves to (sd card, obviously). using adb... well if one can make one's aunt fly out of window, then one can probably figure out that adb is a communication layer between your COMPUTER and your android device, and the most logical place for a log file to be saved to when using that type of connection would be where you're doing your actual development.... on your computer, not your phone.

sdk... software developer kit. the directory where your development is happening on your computer. the main parent folder where you are running adb from.

oooooooooooooh, we all live in a yellow submarine, a yellow submarine, a yellow submarine. Oh, we all live in a yellow submarine.... all together now .... submarine, a yellow submarine.

erm, huh. sorry, was trying to lighten things up a bit LoL ;-D

cheers all!

Don't worry, be happy! :p:D:eek:
 

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
First the "good" news:

Las_Venturax-0.6.2.zip (multiupload)
  • Scheduler tweaks (restored latency to 6ms and enabled hrtick - this time for real!)
  • SmartassV2: a few bug fixes.
  • Some upstream updates (thanks arco)

It seems I have messed up a bit with the 0.6.0 release (and consequently with the 0.6.1 release which was pulled shortly after release because of this): My scheduler tweaks in that version seem quite awful - at least in terms of responsiveness with ADW launcher which I use.
Am I the only one who noticed this? :eek:

Another great "success" in this area, is that I went to a decent effort to add support for the HRTICK (in the 0.6.0 release) but never actually activated it....

0.6.2 fixes this, and I believe is much more responsive, possibly even the most responsive I have ever seen my hero.

Is it all in my head? Any feedback will be welcome :)

Unfortunately, between finding new bugs in the kernel each day and some other RL issues, I will not have time to make any progress on Floyo this week. I will not give another ETA - will just have to eat my hat again.... But I am almost done with my work on the kernel(s) for now and will be concentrating on Floyo next week :D.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    This is a CM6-based ROM with app2SD and custom optimization for the GSM Hero :D

    Experimental 1.4 version posted on 2nd post

    This post has the latest ROM, themes and optional updates (after the themes).
    The 2nd post has the change log, troubleshooting and general comments.
    The 3rd post has comments about development and the source for this ROM.
    Old versions are in the attic on the 4th post.

    Floyo 1.2.0
    (screen shots not updated from 1.1.9 but it looks the same)

    floyo119.png


    >>> Download Links <<<
    Floyo 1.2.0 ROM - mutliupload
    Floyo 1.2.0 ROM - Wupper
    Floyo 1.2.0 ROM - Desean
    Floyo 1.2.0 ROM - mediafire

    Please also take also read the general comments and change log while you are downloading.

    From my experience a full wipe is required when upgrading from previous versions to ensure full stability. But you can always try without it, and only if you have problems then do a full wipe (data, cache and ext partition)....

    Themes (for Floyo 1.2.0)

    Built-in status bar themes

    You can change the theme of the status bar, in the CyanogenMod Settings, under User Interface, Tweak Extras, Select a theme:

    floyo119sbthemes.png


    Sense status bar

    floyo118sensebar.png

    After installing the update, you need to go into the CyanogenMod Settings, under User Interface, Tweak Extras, and select a theme STOCK_Sense.
    Download Sense status bar (mediafire)

    CM Untouched Theme (fixed on 15/12/2010)
    After installing the update, you may need to go into the CyanogenMod Settings, under User Interface, Tweak Extras and select Reset UI tweaks.
    Download CM untouched Theme (mediafire)

    Floyo Original Theme
    If you flashed one of the above themes, and want to go back to the original theme:
    Download Floyo Original Theme (mediafire)
    After installing the update, you may need to go into the CyanogenMod Settings, under User Interface, Tweak Extras and select Reset UI tweaks.

    BRijpstra's excellent blueMAGNUM Theme
    http://xdaforums.com/showthread.php?t=806627

    Thats it for now.
    Themes for other ROMs or previous version will not work or make trouble.

    If you develop a theme for Floyo, let me know and I'll add it.
    If you are an experienced on the graphical side of theming, and are interested, I would be happy to help to compile a theme for Floyo (contact me by PM).

    Optional Updates

    * Full Google Apps
    The ROM only includes the most basic google apps. The Car Home, ChromeToPhone, Google voice, etc. missing apps can be installed with the following update:
    Full Google Apps - based on 2010-09-30 update - Desean (mediafire)

    * GPS config:
    Europe (default)
    US
    Asia
    The default config is Europe. These update change the NTP_SERVER server in the gps.conf accordingly.
    Flashing the one appropriate to your continent can help the lock speed.

    * Replace System Launcher 1.1 (mediafire)
    Floyo comes with the ADW Launcher by default.
    If you wish you can install a different launcher, i.e. Launcher Pro and use the above update after you have installed the new launcher to your "internal memory". The update will remove your current launcher (ADW) from the system partition and move the launcher from "internal memory" (Launcher Pro) to the system partition (to make sure your phone is usable even without the SD card).
    ReplaceSystemLauncher-1.1 supports LauncherPro, Zeam, Home++ and ADW.

    If you want to restore the ADW which came with Floyo 1.2.0, here it is:
    ADW 1.2.0 (Floyo theme)
    ADW 1.2.0 (CM untouched theme)

    * Ubuntu Fonts (mediafire)

    * Original CM6.1 Fonts (mediafire)

    * App2SD and Compcache for official CM (Floyo already includes it)
    This is a rewrite of the apps2sd, more in the lines with the infrastructure that already comes with the CM sources. I hope this rewrite will improve its stability. This is the version included with Floyo 1.2.0. It is intended to be installed on the "official" CM releases which do not have app2sd built-in.
    It will use the ext partition (if such exists) for all apps which do not support the new floyo app2sd method (see more details on the second post of this thread).
    Finally, regarding compcache, this will make the compcache option in the CM settings work (if you have a compatible kernel like flykernel-12pre2). I doubt that the compcache, will help CM - in fact I would guess quite the opposite and hence I do not recommend it. But who knows, let me know if you find differently.

    Thank You!

    - Floomat for the everything! Boot animation and much of the icons and themed stuff in the ROM is thanks to him.
    - Wayferer for the theming and icons!
    - Moonshield for the thorough testing.
    - Desean for the hosting :)
    - CyanogenMod for their excellent work (99% of this ROM is theirs)

    And thanks to everyone that reports bugs and further ideas to improve this ROM.



    Donations are always welcome and accepted but are in no way required.
    7
    General comments and change log

    (troubleshooting section is in this post below the "Instructions and comments")

    Experimental version:

    Floyo 1.4pre1 ROM (Android RTK)
    Floyo 1.4pre1 ROM (Desean)

    I suggest you also flash the following fixes on top of it:
    Floyo 1.4pre1 MapFix (Android RTK) - Fixes crashes in some GPS tracking apps (I hope)

    I assume a full wipe is needed, even when coming from 1.2.0, but you can also try without it and see what happens.

    This is a major upgrade from the 1.2.0 version, with the following updates:
    - Based on the latest sources for CM6 (6.2.0+)
    - Backported some stuff from Gingerbread/CM7 like: new LatinIME keyboard, new ADWLaucher, overscroll glow, CMParts CPU Settings
    - Latest Arabic and Hebrew support (backported latest fixes from CM7)
    - Theme retouched taking some icons from Gingerbread
    - Updated google apps
    - OpenGL 1.1
    - Fully ODEXed with dalvik2cache in addition to the regular app2sd for maximum performance :D
    - Tweaked low memory values and added further tweaking of SD card
    - Added CMParts settings to change scheduler latency (works only on FlyKernel). Read more about this here.

    Latest Changes

    Floyo 1.2.0
    - Updated sources to CM 6.1 release
    - Apps2sd rewritten for better stability
    - Compcache support added (but not recommend)
    - Themes rebuilt, hopefully more stable this time
    - FlyKernel-12-pre2


    Instructions and comments

    * Upgrading from another CM6-based ROM - even 1.1.8 (sorry):
    To ensure 100% that there are no problem you must do a FULL wipe.
    You can try installing the new version over your old CM6 based ROM, but if you have problems please do a clean install before reporting them.

    * Mobile data is disabled by default - enable it if necessary under wireless settings, mobile networks.

    * This ROM included both the "old" app2sd and the new froyo native app2sd.
    The froyo native app2sd means that apps which support it will be installed to the main partition of the SD card (under .android_secure). Currently very few apps support it. You can move apps manually to the SD, but it is not recommend as this can cause problems, especially with programs with widgets and such.
    The "old" app2sd means that if you have an ext partition on your SD card, it will automatically be used for the apps that do not support the froyo app2sd.

    * This ROM uses FlyKernel-12pre2.
    By default the ROM will boot at 576/352 (no OC). You can use SetCPU to change the speed.
    When I release FlyKernel-12 (final), which hopefully should not be far, the FlyKernel page will include different packages of the kernel which can boot at different speeds (like the 11c kernel currently has).
    Notice that with FlyKernel 11's smartass governor you don't need a sleep profile any more : - same thing with FlyKernel 12)

    * JIT is by default on. You can disable in the CyanogenMod settings menu, but no reason to do so, really.

    * If you have problems with MMS, please check your MMS settings and make sure they are correct.

    Troubleshooting

    *) Most problems people report, are fine for most, and the problem is "specific" only to "you". In order to help isolate the root of such problems (i.e. some app you installed but others did not), I propose the following "fail safe" way:
    (if according to your common sense you think you can cut some corners and aren't following my instructions to the letter, thats perfectly fine just detail in your report exactly what you did do to isolate the problem!)

    a) If necessary, make a nandroid backup (nand+ext) of the current state of your ROM. This way you have nothing to loose, you can always go back to your current state.
    b) From RA recovery 1.7.0.1, do a full wipe (both the "data/factory reset" and the "SD:ext partition" from the wipe menu). I assume that previous versions of RA recovery might also work, but highly suggest you upgrade to 1.7.0.1. About clockworks recovery, I have not tested and do not know if it is fully compatible with this process.
    c) Install only the basic ROM update (Floyo-1.2.0.zip), and, if necessary, install only the updates and apps you must in order to recreate the problem.
    d) Check if the problem still occurs. If the problem persists, please report it with as much details as possible.
    If it is solved, continue to install/configure the ROM to your liking and follow if and when the problem returns.
    e) If you wish, you can now go back to the nandroid backup you prepared in the first step.

    *) When reporting an issue, please detail as much as possible. The level of detail should ideally be such, that if I decide to devout time to this, I will be able to recreate the problem on my device.

    *) When reporting battery life, please try to test it for at least a couple of days and report what settings you are using (kernel, governor, speeds, etc.), what and approximately how much you use the phone and the battery life you are getting.

    *) If you are getting FCs(force close messages that kill apps when they shouldn't die), please attach a logcat to your post. In order to generate the logcat with adb, use a command such as this:
    Code:
    adb logcat > logcat.txt
    You should close the adb window after you recreate the problem.
    Another option to get the logcat, is to use a program from the market but I am unfamiliar with this.

    * If you are stuck in a bootloop, please include the logcat from the beginning of your boot, by running the above adb command ("adb logcat > logcat.txt") from either before you turn on your phone or relatively close to the start of the boot.

    * If you have spontaneous reboots of the phone, please attach the last_kmsg, which you can get with a command such as:
    Code:
    adb pull /proc/last_kmsg

    History

    Floyo 1.1.9
    - Floyo theme tweaked a bit
    - Gallery3D internal options tweaked - should work even better now :)
    - Notification fix further fixed (i.e. low battery light)
    - GPS fix integrated (this has been updated upstream as well :))
    - Market version is the one from Elelinux market fix.

    Floyo 1.1.8
    - New Floyo theme
    - Fix notifications - should now work good both with LEDs and/or jogball :)
    - In-call touch UI disabled by default, can be enabled in settings
    - Mobile disabled by default (to avoid unnecessary traffic on first boot)
    - Updated to latest CM source and what a update :D Things I noticed and enjoy:
    New power controls in status bar, Screen rotating jumpiness has been fixed, Gallery 3D rotation fixed and it finally has decent performance, Updated ADW
    - FlyKernel-11c

    Floyo 1.01
    - Fixes power button on lock screen (reboot menu still disabled but screen off will work).
    - Fixes jogball notifications and ringing under certain conditions.
    - Volume selection now includes both vibrate and silent modes (unless vibration is disabled).
    - Disabled "animation" of auto brightness
    - Sound Recorder is now visible in app list.

    Floyo 1.0
    - FlyKernel-11
    (Which includes fixes for camera freezes and booting with USB connected)
    - Changed notifications to work with jogball light.
    Meaning all notification will be only with Jogball, LED only for battery status.
    - Reboot menu now blocked when phone locked.
    - Charging light will turn green only when reached 100%.
    - Improved RTL fix (with blocks of numbers).
    - Updated CM sources from October 2nd, which includes lots of goodies like the "stock" file manager, swiping notifications away and much more I didn't even notice.
    - Update google apps.
    - Sense status bar tweaked to look better.

    Floyo 0.8
    - App2SD - see note below
    - Added Facebook & HTC_IME keyboard
    - RTL fixes - mainly mixing of RTL with numbers/LTR
    - Tweaked ADW settings to perform better
    - Changed status bar appearance to a sense-like look
    - Added ringtones and sounds from HTC
    - Gallery3D has rotation disable (only landscape mode) because rotation is very buggy
    - Also included Gallery 2D which works better (but does not look as nice)
    - FlyKernel 10a
    6
    Long overdue update:

    Experimental version:

    Floyo 1.4pre1 ROM (Android RTK)
    Floyo 1.4pre1 ROM (Desean)

    I assume a full wipe is needed, even when coming from 1.2.0, but you can also try without it and see what happens.

    This is a major upgrade from the 1.2.0 version, with the following updates:
    - Based on the latest sources for CM6 (6.2.0+)
    - Backported some stuff from Gingerbread/CM7 like: new LatinIME keyboard, new ADWLaucher, overscroll glow, CMParts CPU Settings
    - Latest Arabic and Hebrew support (backported latest fixes from CM7)
    - Theme retouched taking some icons from Gingerbread
    - Updated google apps
    - OpenGL 1.1
    - Fully ODEXed with dalvik2cache in addition to the regular app2sd for maximum performance :D
    - Tweaked low memory values and added further tweaking of SD card
    - Added CMParts settings to change scheduler latency (works only on FlyKernel).

    As you can see, I put quite a lot of effort into this version trying to improve performance and add some updates while keeping stability.
    This version hasn't been tested enough yet, hence the label "experimental". When I release the final version, I'll add more themes, screenshoots etc.. If there is a demand for it, I can also release a deodexed version for the final version, although I am not sure what other than disadvantages does a deodexed ROM bring to the user (it is a bit more work for me though :p).

    Regarding the Scheduler's latency: In FlyKernel-12a, I had tweaked the scheduler towards good gaming performance (i.e. neocore benchmark). There where many complains that this hurt responsiveness (vibro bug?), although to tell the truth I don't notice it.
    The main parameter to play with here, is the scheduler's latency. In theory lower values should increase responsiveness, while higher value cause it to behave more like BFS and increase gaming performance. The default value in the current kernel is 6ms (like LV as far as I know). The default in FlyKernel-12a was 60ms.
    In this ROM, you can very easily control this value yourself, go to the CyanogenMod settings, under performance, CPU Settings, there is the "scheduler latency" setting. Note, that this setting will only appear with FlyKernel-12b, as on other kernels the permissions to change this are too limited. Apart from this change (and changing the default latency to 6ms) there is no difference between the FlyKernel 12b version and 12a.

    Let me know what you think about the ROM and about the different latency values.
    5
    Source and CM development (Updated for Floyo 1.2.0)

    This ROM is completely open source. It is based on the sources of CyanogenMod with a few repositories which I have forked (Frameworks base and policy, htc hero device, cyanogen vendor, CMParts and Gallery3D). The updated sources to my forked repositories are mainted in my github. The kernel sources are also in my github.

    General Froyo building

    Building CM from the sources is described very nicely here:
    http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero
    I suggest you start with this (or even with a pure ASOP build from the google sources as described here).

    CM itself is an easy and convenient platform to develop on. Additionally they have implemented the gerrit review system which can be used to suggest changes back to the CM mainstream - read more here.
    If you are serious about "CM development", I would consider starting with the clean CM repositories (many of my changes are a matter of personal taste). You can still take a look at my Floyo sources and build process (described below) to help you get started.

    Building Floyo

    If you want to build the ROM with my (personal) tweaks, you need to use the changes in my forked repositories.
    One simple of way, of doing that is replacing the .repo/manifests/default.xml file with the attached manifest.xml file and then doing "repo sync" (or "repo sync -j 8" which is faster ;)).
    Finally you will also need the proprietary files, some are the google apps which are updated all the time and some are specific to our hero (and will prolly not change at all). To make it easier for you here are the proprietary files I used to build Floyo: floyo120-vendor-proprietary.tar.bz2.

    Assuming you have already done the initial configuration (installed all required packages for the build environment and etc.), the steps to download my sources and build them should be something like this:

    * Init CM repo:
    Code:
    repo init -u git://github.com/CyanogenMod/android.git -b froyo

    * Replace the .repo/manifests/default.xml file with the attached manifest.xml file. I suggest you also commit it, because I have had occasional errors if it's has uncommitted changes:
    Code:
    cd .repo/manifests/
    git commit -am "use floyo repositories"

    * Download source (will take a while):
    Code:
    repo sync  -j 8

    * Extract the floyo120-vendor-proprietary.tar.bz2 (in root directory).

    * Select Hero build:
    Code:
    source build/envsetup.sh
    lunch cyanogen_hero-eng

    * Build update package:
    Code:
    make -j4 bacon

    Let me know if you have any trouble.

    Feel free to contact me if you need any help. I will try to help anyone interested in developing on the CM sources (with my tweaks or directly) as best my free time will allow.
    4
    After much debate (amongst myself), I have decided, that since I need to update Floyo for myself, I will cross my fingers really really hard and release 1.2.0 without too much testing :eek:

    Floyo 1.2.0
    - Updated sources to CM 6.1 release
    - Apps2sd rewritten for better stability
    - Compcache support added (but not recommend)
    - Themes rebuilt, hopefully more stable this time
    - FlyKernel-12-pre2