Root KaosFroyo v27

[Frisco]

Dev's thread at XDA:

http://forum.xda-developers.com/showthread.php?t=685594

Download v27:

Multiupload.com - upload your files to multiple file hosting sites!

I got into this one at about 5 pm yesterday and did my usual settings and tweaking here and there, stuck with the default ADW launcher and did not overclock.

The first thing that came to my attention as I was navigating the menus and using Market, etc, was the speed; for some reason this version gives me the perception of better snap from one screen to another, menu to menu and browser loading, etc.

Most often I turn off animations right away to help with battery life and resources in general, not to mention they annoy me, but I left them on for a while longer just to see if it would slow things down after a few hours of use, but nothing slowed down. I turned them off anyway.

There are duplicate "Android Keyboard" menus in the main Settings "language and keyboard" hierarchy. Other than that the whole thing seems set up nicely and with no other goofiness that I could find, so far.

I think 2.2 fans will really like this ROM by Kaos; it seems to have the known bugs from previous versions stomped completely out, not the least of which is a now perfectly working stock camera, fixed in v25.

Here are the change logs for the past three versions, including v27:

CHANGELOG:

V27
Fixed softkey backlight BETTER
Fixed PPTP creation bug
Fixed missing font issue
Removed some duplicate APKs
build.prop minor fix (thanks jphenow!)

V26
Fix GPS regression in V25.

V25
Latest ADW
Fix softkey lights
Fix streaming audio issue(Mostly Pandora)
Fix Camera preview
Enabled 5MP camera
Video recording works
Update to latest bleeding edge framework.
Fixed Gallery rotation bug.
Added Mixer/DSP app.

 

[shaylih]

I tried using kaosfroyo and other froyo roms, but for some reason I kept getting an error saying my sd card had to be formatted so I flashed back to my previous rom. I use apps2sd. So far the apps2sd work with the 2.1 roms I've tried (xtr, droid does, white widow), but none of the 2.2. Anyone else having this issue?

 

[shh]

I tried using kaosfroyo and other froyo roms, but for some reason I kept getting an error saying my sd card had to be formatted so I flashed back to my previous rom. I use apps2sd. So far the apps2sd work with the 2.1 roms I've tried (xtr, droid does, white widow), but none of the 2.2. Anyone else having this issue?

FroYo uses apps2sd differently than other roms. After making a backup of everything on your sd card to your computer, format the sd card. Add your FroYo rom to the sd card (root dir) then go into recovery and flash the new FroYo zip. I have two sd cards that I exchange when the urge strikes me. One is setup for FroYo roms (PunkKaos v27 & CELB 1.8) and another with the apps2sd partition and I have (XTR Rom 3.1 and XTR Sense) on that one. Now that the PunkKaos has got v27 of his FroYo in such great shape I probably won't be switching so often.

Hope this helps.

 

[copestag]

I tried using kaosfroyo and other froyo roms, but for some reason I kept getting an error saying my sd card had to be formatted so I flashed back to my previous rom. I use apps2sd. So far the apps2sd work with the 2.1 roms I've tried (xtr, droid does, white widow), but none of the 2.2. Anyone else having this issue?

this is because the 2.1 roms require you to partition your SD card for A2SD..... which you have obviuosly done...... and it works

however.... froyo requires you to have an SD card that is NOT partitioned....... this is why you need to format your SD...... you have to get rid of the the partition for it to work

 

[shaggylouie]

Well then. I guess I'll have to try this one out too. Thanks for the report Frisco.

 

[Frisco]

Well then. I guess I'll have to try this one out too. Thanks for the report Frisco.

You're welcome, shaggylouie.

I'm hoping you've taken note of post #4, etc, about the sd card if aps2sd is of interest to you.

Incidentally, along the lines of an update to my testing of this ROM, I've overclocked to 710/710 with a sleep profile of 245/245. This brings the ROM up to a speed I'd not yet seen in a 2.2 on my Eris, and with no anomalies so far (overclocked about three hours ago).

 

[teegale]

Installed and setup setcpu, and my phone is running like a champ. This is the first time I've ever rooted or used a custom rom. Love it! Thanks.

I'm using 710/528 ondemand.

245/245 screen off

 

[shaylih]

Thank you so much for explaining. I'll try it later.

 

[Lagos]

I tried this rom last night. Pretty good so far! Hopefully the developer will be able to get more speed tweaks out of it in the future.

 

[shaggylouie]

I'm hoping you've taken note of post #4, etc, about the sd card if aps2sd is of interest to you.

It's funny you mentioned that. I actually had to go back to a FAT32 format to try out Cyanogen, and since then I've kept the same formatting. I'm back on xtrROM 3.03 (my personal favorite), but I will definitely be testing Kaos v27 soon. I will compare it's "snap factor" to xtr and report back later.

 

[srmccoy]

v27 pulled me away from XTR as my standard ROM. I was having some odd issues with XTR, primarily sync loops that were eating my battery. I went from 100-10% in about 4 hours with my normal usage. I watched a 48 minute youtube video over wifi, and went from 85% battery to 19% in that timeframe.

Kaos has fixed all of my issues with 2.2 and it now has every feature, and the speed, that I require from a standard ROM. The battery life is also the highest I've seen. It lasts me a full day with my normal, fairly heavy usage.

 

[Haxcid]

So what do you think Frisco, does it compare at all speed wise with xtr? Should I give it a look.

 

[Frisco]

So what do you think Frisco, does it compare at all speed wise with xtr? Should I give it a look.

It is not as super fast as any of the xtrROMs I've had, and as you know 3.0.3 is my default OS.

Compared to other 2.2s it's faster and just better put together.. it feels like it's coming to the point where it is very close to being the finished product and I dare say that it is changing my mind about whether 2.2 can be run in the Eris as naturally as 2.1.

I did overclock to bring it up fairly close to unclocked xtrROM 3.0.3 speed, but this Kaos v27 really does not need the CPU pushed at all, in my opinion. ymmv

 

[bjf88]

I agree Frisco. I moved back from my first ROM, Cyanogen Tazz Froyo, to xtrROM because of the overall lag I was running into. Moving to xtr was like night and day. But when I flashed this one this morning I was pleasantly surprised by the speed. Loading the manage applications is close to instant! Thats usually how I judge speed... haha. Really liking it so far!

 

[Frisco]

I want to see how this goes over several days.. I do recall Tazz and the v24 of Kaos getting progressively slower despite my routine maintenance.

I'm hoping that's all been resolved.

 

[ttran97]

What are the main incentives for switching over to Froyo? With xtr, you can already do app2sd, jit, and overclock. I'm just curious. I'll probably end up flashing KaosFroyo later today anyway. hehe.

 

[Frisco]

What are the main incentives for switching over to Froyo?

I see none, other than having the most evolved Android OS the Eris can handle at this point in time.

2.1 is very nice as it is, I agree.

But then, I felt that way about 1.5.

 

[Toolanddiemaker]

I went from V24 to V27 last night and I think you are right on Frisco, eveything I have ran thru it's paces, clean and fast. KaosFroyo is my go to rom now. Enjoy.

 

[bjf88]

My favorite thing about Froyo is that the market remembers your apps and will automatically start to download them when you boot up for the first time. And you can set all apps to automatically update. Market search is much better also. Apps2sd without partitioning. Better application manager. More settings options.... try it and see!

 

[droidhiker]

I want to see how this goes over several days.. I do recall Tazz and the v24 of Kaos getting progressively slower despite my routine maintenance.

I'm hoping that's all been resolved.

Thats what got me to switch to xtr. I liked Tazz a lot but the lag increased and that was one of the main reasons I rooted so I can get rid of lag. I will be watching to see how v27 of Kaos is going. I did like the look and feel of 2.2

 

[shaggylouie]

First impression of v27 (literally minutes in) is that it is definitely faster than before. Snap factor = less than xtr, but better than any other froyo. I need to spend more time setting it up. Might run it through the weekend.

Are you guys keeping JIT on or off? I just did a VERY brief try out without JIT on and did not notice a difference. Maybe because I'm clocked over 710.

 

[Frisco]

First impression of v27 (literally minutes in) is that it is definitely faster than before. Snap factor = less than xtr, but better than any other froyo. I need to spend more time setting it up. Might run it through the weekend.

Are you guys keeping JIT on or off? I just did a VERY brief try out without JIT on and did not notice a difference. Maybe because I'm clocked over 710.

That about JIT and overclocking is one of the questions I'd like to see input about. I have a suspicion that both features are contributing to the compatibility of 2.2 with Eris and its dinky CPU, but that if we take away one, the other will shore up the functionality to good levels.

Sort of like having 2 horses pulling a wagon vs just one of them; a horse can only run so fast and 2 can't run faster than one.

 

[Haxcid]

Does tethering work?

 

[doogald]

Does tethering work?

I believe that the built-in, Froyo tethering does not yet work, but third party tethering apps from the market will.

 

[srmccoy]

KaosFroyo is overclocked by default to 710/245. For some this is fine, but I prefer to have smaller gaps between clock speeds. Jumping from 245 at rest to 710 causes some hiccups. So I set my SetCPU profiles as I normally do: 710/528 normally, 245/480 with screen off, and 245/245 Failsafe at 45C. Makes everything feel more snappy.

I find that the OS gets faster after a couple of days, primarily because stuff gets cached and you tend to fill up the memory by that point. I actually try not to reboot because of this.