ARCHIVED: [ROM+Kernel] ~*~ Bumblebee 2.4 ~*~ (6/25/2011)

Status
Not open for further replies.
Which version Xionia CWMA recovery were you using that gave you the problems?

It was .6.
I've since flashed to .4, but I have not yet tried installing Bumblebee with it. If the other people using CWMA .6 are the ones with issues, that may be the culprit, especially with obi confirming it flashes just fine with .4.

-K
 
Yeah seems that those of us using .6 were having the issues and that .4 will work. I am now using this kernel with Rodimus. It booted crazy fast and the boot ani doesn't freeze up anymore. I can tell when the OC on boot kicks in from the boot ani lol. Only problem is that my accelerometer isnt working anymore. Not sure why but eh...

Update: Tried flashing mmarz file for fixing some files from the Xionia kernel that he posted in the picasticks thread but didnt work.
I think I'll try going into recovery, flashing the fix again, then flashing this kernel over it and see if that fixes it.

Update #2: The accelerometer does work without going in and reflashing. Works if I have an app open but it doesn't work on the home screen. Not that I care since I don't use it in Landscape mode for anything but Pandora and Navigation while I'm driving.

Still loving this Kernel on Rodimus...phones the fastest, response wise, that it's been since I originally opened up the packaging.
 
Last edited:
Am I like the only person who uses thunderc-v-1.2.0-GNM recovery? I think it's superior. I like the extended sd card format options, for ext3, and ext4. I don't think CWMA has it.
 
Yeah seems that those of us using .6 were having the issues and that .4 will work.

.4_virgin is the last (only?) xionia cwma recovery specifically compiled for the V. It seems that .6, and other recoveries made for the S, will work most of the time for us, but there are some common issues that people report which aren't present if the .4_virgin recovery is used. (There actually may still be some issues with .4 since it was ported over from the S codebase, but they are fairly minimal).

If you've wiped and try to install the Bumblebee ROM but get a blue screen or some other reboot issue, then your recovery probably didn't do the wipe properly and left some residual files from the old ROM that conflict with the Bumblebee kernel.

I will be releasing my own Virgin-only recovery soon that should resolve these lingering problems people are having, and not just this ROM -- when people try to flash from one ROM to another, even after wiping, there are repeated problems with these S-based recoveries.

I am now using this kernel with Rodimus. It booted crazy fast and the boot ani doesn't freeze up anymore. I can tell when the OC on boot kicks in from the boot ani lol. Only problem is that my accelerometer isnt working anymore. Not sure why but eh...

Update: Tried flashing mmarz file for fixing some files from the Xionia kernel that he posted in the picasticks thread but didnt work.
I think I'll try going into recovery, flashing the fix again, then flashing this kernel over it and see if that fixes it.

Update #2: The accelerometer does work without going in and reflashing. Works if I have an app open but it doesn't work on the home screen. Not that I care since I don't use it in Landscape mode for anything but Pandora and Navigation while I'm driving.

There is a launcher setting that controls this (Menu->Settings->Display->Auto-rotate Screen). The launcher is part of the ROM, not the kernel. If you're not using the stock launcher, this setting may be somewhere else. I don't know whether Romidus uses the stock launcher or not.

Still loving this Kernel on Rodimus...phones the fastest, response wise, that it's been since I originally opened up the packaging.

Glad you're liking the kernel. :) More stuff is on the way...
 
Ok I tried flashing this rom/kernel with all 3 of the recoveries, 4 if you count .4 and .6 seperately, and still get the blue fastboot screen. For testing purposes to eliminate a phone issue I flashed ALL of the other roms and they all still worked for me except this one. I even did a nandroid restore from right after I originally rooted my phone so everything was completely stock. Still having this issue. I started having fc on launcher last night on Rodimus/BB to tried these again with no luck. :( Guess I'll have to keep trying as I really want to give this a shot. :D

Update: Got this to work due to my willingness to fail a lot before I succeed lol. I had to, or this worked, use .6 to flash my nandroid backup. flash clockwork mod recovery. wipe everything. install the rom. wiped cache/delvick, installed kernel.
FINALLY GOT IT TO BOOT! woohoo
 
Last edited:
Ok I tried flashing this rom/kernel with all 3 of the recoveries, 4 if you count .4 and .6 seperately, and still get the blue fastboot screen. For testing purposes to eliminate a phone issue I flashed ALL of the other roms and they all still worked for me except this one. I even did a nandroid restore from right after I originally rooted my phone so everything was completely stock. Still having this issue. I started having fc on launcher last night on Rodimus/BB to tried these again with no luck. :( Guess I'll have to keep trying as I really want to give this a shot. :D

Ok, try this for me if you can: see first post for full-wipe zip
This update zip is the same ROM and kernel, but it includes it's own wipe (it actually formats the data, cache, and system partitions before installing).

Let me know your results.
 
Last edited:
I'll try it in a bit. Going to do a nandroid back up of my current set up. Went back to Rodimus/BB Kernel as I love some of the things between his rom and your kernel that enable things so i can avoid using other apps. His lock screen for one. Plus his zip to remove the clock from the status bar. Your default OC at boot is awesome too. I fully appreciate the work that you two and many others have put into getting things where they are today.

Update when I'm done. :)

UPDATE: Obi that worked great. Just flashed over my Rodimus/BB setup without doing any manual wipes and everything works great. Didn't even have to re-install my apps. FYI...this is the first time I've flashed a ROM and not done a complete wipe before hand. Awesome job and thanks for the quick help in fixing this. You, sir, are another great dev added to a great community.
 
Last edited:
For anyone wondering, bumblebee's kernel seems to work just fine on Harmonia 1.0. I had to make the switch from Picasticks kernel, as the ext modules were not working for me. Which is needed if you want to use Links2SD, app2ext, etc...
 
Has anyone been able to get 100 hours per charge like OP?

Just to clarify, what I said was that I get about 1% drain per hour when the phone is idle (by which I mean that the screen is off but the phone is still on). If I set it aside for 3 or 4 hours without touching it, there will only be about 3% drop, sometimes less. The other day I unplugged the phone at 7AM, got no calls or texts and didn't look at it until 10AM, and it still showed 99%. I haven't tested to see just how long it will last in an idle state, since I actually do use it. :) Of course this also highly depends on what apps you're running, whether they run in the background, whether widgets update even with the screen off, etc.
 
I've noticed that my phone will go several hours before it moves from 100%, but after that it seems to lose about 2-5% per hour.
 
I've noticed that my phone will go several hours before it moves from 100%, but after that it seems to lose about 2-5% per hour.

I've noticed that too. I have deleted the battery stats file but it still does it.
 
First time installing a rom. Is there a way to check if the kernel has been installed correctly?

Everything seems to work but I could not get ext3 partition to work so I had to switch to FAT32.

The battery usage seems to be about same as the stock setting.
 
First time installing a rom. Is there a way to check if the kernel has been installed correctly?

Everything seems to work but I could not get ext3 partition to work so I had to switch to FAT32.

The battery usage seems to be about same as the stock setting.

If you look at the "about phone" section it will tell you which kernel is on your phone.
I, nor has anyone else I've seen, had issues using ext partitions. I use ext3, it's what CWMA .6 creates by default, and I have had no issues at all. I use Link2SD...which method are you trying to use?
 
First time installing a rom. Is there a way to check if the kernel has been installed correctly?

Everything seems to work but I could not get ext3 partition to work so I had to switch to FAT32.

The battery usage seems to be about same as the stock setting.
I had the same problem and I am having to use FAT32 for it to work. I also had this problem with picasticks kernal too.
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,903
Messages
6,970,528
Members
3,163,646
Latest member
Chris34728