• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root KaosFroyo v34

stanlalee said:
do you have the link to the CFS kernel zip. I'm not having scrolling or lag issues with the BFS (probably because I only have 3 screens and dont scroll much) but I'd like to try it to see if it helps v34 (or I could wait for v35 to come out which has it I guess. had v33 all of two days before I noticed v34 was released lol).
Click to expand...

The CFS kernel can be found in this thread: [GPL]2.6.29.6 CFS Kernel V4 9/6/10 - xda-developers

I downloaded the V4. Just flash it from recovery like a ROM. Wiping data is not required (in fact, you probably do not want to do that), but I would wipe Dalvik cache from recovery before or after flashing the kernel before rebooting the phone.
 
Not sure if this is something new or not, but if you guys want the Black Bar (Black Notification Bar), here's the steps:

Go to Settings > CyanogenMod settings > User Interface > Tweaks Extras

From there, hit "Select a theme" (you may want to save your current one if you've been messing with the notification bar settings)

Hit "STOCK_Black"

Back out, hit ok (saying to reboot to see changes), reboot, and voila!
 
Damn, Im still on V32! Ah! Alright Ill download it now...sigh lol, it is becoming a chore :D

would it be safe to flash directly from V32 to V34, or should I do V33 and then V34?
 
Familyguy1 said:
Damn, Im still on V32! Ah! Alright Ill download it now...sigh lol, it is becoming a chore :D

would it be safe to flash directly from V32 to V34, or should I do V33 and then V34?
Click to expand...

My understanding is that V33 was something of a problem child and many folks went back to V32 and then jumped to V34 when it was released. So there doesn't appear to be any reason to flash V33 on your way to V34.
 
All of the Kaos Froyos are complete packages. You can flash from any version to another.

If going to V34, I would data wipe, but you could try without. Definitely wipe dalvik if you are going to try without wiping data.

I'm also going to suggest flashing the better CFS kernel (V4 here: [GPL]2.6.29.6 CFS Kernel V4 9/6/10 - xda-developers ) if you are going to V34. Flash KF V34, then flash the kernel, then wipe Dalvik and restart.
 
mhotovec said:
My understanding is that V33 was something of a problem child and many folks went back to V32 and then jumped to V34 when it was released. So there doesn't appear to be any reason to flash V33 on your way to V34.
Click to expand...
I've had no problems at all with v33 I got very comfortable with v30 but the nav lag was becoming a big problem for me, as I drive truck for a living so for me, v33 is pretty much v30 with out the nav lag so i'm happy :D is there anything i am missing out on by not jumping on v34?
 
Due to low signal bard (as always) I attempted an update using *228 and found that in that situation I had no way to get my dialer back to choose option 2... The screen just had an android on it, and said that my phone was being programmed. The key to bring the dialer back up was not there... Has anyone seen this? Am I missing something? BTW LOVE Kaosfroyo v34!
 
JakeJB said:
Due to low signal bard (as always) I attempted an update using *228 and found that in that situation I had no way to get my dialer back to choose option 2... The screen just had an android on it, and said that my phone was being programmed. The key to bring the dialer back up was not there... Has anyone seen this? Am I missing something? BTW LOVE Kaosfroyo v34!
Click to expand...

Yep, that is also in the FAQ, I believe. KaosFroyo FAQ - KaosFroyo - GitHub

Long-hold the menu softkey while you are in a call to get the keyboard to pop up, and from there you can enter a 2. Or you can dial *22899 to get it to automate the option 1 and option 2 in the same call.
 
JakeJB said:
Due to low signal bard (as always) I attempted an update using *228 and found that in that situation I had no way to get my dialer back to choose option 2... The screen just had an android on it, and said that my phone was being programmed. The key to bring the dialer back up was not there... Has anyone seen this? Am I missing something? BTW LOVE Kaosfroyo v34!
Click to expand...

*22899 did the trick...
 
How stable is this rom? I am currently running kayosfroyo 30 and not having any issues, with the exception of the gallery.
Any major benefits to switching? I flashed cyanogen 6.0 yesterday and that locked up my phone occasionally plus force closed LP. I restored KF30.

Anymore input on version 34 would be greatly appreciated.
 
This is probably a really stupid question, but I don't get it if you want to go Launcher pro you flash the ADW-b-gone.zip got that. Then you download it from the Market? Where does it put it?
 
If you've installed Launcher Pro and you're looking for it in the apps list, you're not going to find it. You can see Launcher Pro in Titanium Backup, and you could probably find the apk file somewhere, but that's about it.
Once you've installed LP press the home button on your phone, you should get a pop-up asking you which launcher you want to use. Select Launcher Pro and you're on your way.
 
Toolanddiemaker said:
This is probably a really stupid question, but I don't get it if you want to go Launcher pro you flash the ADW-b-gone.zip got that. Then you download it from the Market? Where does it put it?
Click to expand...

To add to mhotovec's post, you don't have to remove ADW if you don't want to. I never do. It doesn't take up that much space (about 500 kB.)

But, as mhotovec said, whenever you add an app that could be a launcher - or remove one - the next time that you press the home key, Android will ask which app you want to launch for home, with an option to set that choice as the default from that point on (if you don't choose that option, it will continue to ask you each time you press Home.)
 
So just before my wife let for work today she looked at me and said hey it's been a few days don't you have some new version of my rom to flash?

I must say its been nice not having a new flash every couple of days but I am looking forward to v35.
 
I'm running V32 (waiting on V35) and I've tried d/l the street view addon for google maps but it will not install. I get an error message saying the install was unsuccessful. Anyone else had this problem? Any suggestions for a fix?

Thanks,
RF94
 
rangerfan94 said:
I'm running V32 (waiting on V35) and I've tried d/l the street view addon for google maps but it will not install. I get an error message saying the install was unsuccessful. Anyone else had this problem? Any suggestions for a fix?

Thanks,
RF94
Click to expand...

After some additional searching I found a solution to the above problem. You need to go to system/apps on the sd card and rename Street.apk to Street.bak or you can delete the file. I deleted mine. Reboot the phone and then go into the market and d/l and install the new Street View from Google. Worked like a charm!

RF94
 
Finally updated to version 34. I did a full wipe and Dalvik wipe before I started. I thought your apps were all supposed to come back automtically with the Froyo ROMS? Had to go find all mine again. I know I'm still missing some.

Too busy to set up all my screens now, but the phone and e-mail are up and running, so everything else can wait.
 
So far I am leaning to returning to Kayosfroyo 32.

I am finding the phone to be very laggy.
Launcher Pro keeps force closing.
I switched to the Dolphin Browser and that seems to be working a little better.

I just found the phone to be so much more responsive with version 32.

Any other input?
 
ggangi said:
So far I am leaning to returning to Kayosfroyo 32.

I am finding the phone to be very laggy.
Launcher Pro keeps force closing.
I switched to the Dolphin Browser and that seems to be working a little better.

I just found the phone to be so much more responsive with version 32.

Any other input?
Click to expand...

Do you use SetCPU? Have you switched from the "ondemand" governor to "interactive"? Well, actually, are you using SetCPU at all?

See EU1's post (about Cyanogen Tazz 3.0, but perhaps still relevant): http://androidforums.com/eris-all-things-root/168800-cyanogen-tazz-v-3-0-vanilla.html#post1530453

for the moment I think I should not offer any opinion at all about using SetCPU with the Decad3nce/Conap CFSV2 kernel - I'm having nothing but trouble no matter what settings I use when I use SetCPU (v2.0.2)

The odd thing is that trouble doesn't develop immediately - in the last trial I attempted, I used only interactive governor profiles on a CFS2 overflash of Tazz 2.0, with minimum clocking no lower than 245 Mhz... and the first sign of trouble showed up 9 hours later. (I used the phone for texting and web browsing off and on during that time).

The trouble shows up when you wake the phone from a screen off condition; immediately after that, the phone seems normal but then slows down progressively over time scales of a small number of minutes - perhaps 3 to 5 - eventually to the point of unresponsiveness.

I'll run another pass at the same ROM + kernel replacement; but without the use of SetCPU or Autokiller. In the meantime, I can't say that SetCPU is causing the trouble (I'm not using the widget, BTW), although I think that Decad3nce believes that the SetCPU app is the source of the trouble - I'm not seeing anybody else complaining about their phone freezing up, so that (SetCPU) seems like the first place to look.
Click to expand...

When I installed V34, I did it from a complete wipe and decided to try without SetCPU at all, and I have to say that I was getting great performance, no lag over time, and great battery life to boot. (I am now trying out CELB 2.6, basically with the same results.) If you do go back to V34, or on to V35 and further, and have been using SetCPU, you may want to try without it.
 
thanks for the reply but i never installed set cpu. I am however running autokiller. Do you think that is causing issues?
 
Now when i start the phone the brightness levels are messed up. No I don't have autobrightness checked off.
 
You must log in or register to reply here.
Back
Top Bottom