Ok I tried some new roms and started noticing a pattern in that BLN was behaving erratic.
By erratic I mean this.
If I set the LED's to stay on, they will turn on but then raondomly go off for a second or so and then come back on again, there was no pattern except it took longer to happen after a phone reboot and when the usb plugged in from pc.
If I set them to blink and I set the off period for longer than 4 seconds, then after they go off for the first or send time then after just 1 second they come back on again but only if I set the off to more than 4 seconds, weird.
In these cases was testing on freshly installed roms with wiped user data.
One of the roms was based on stock which made this even stranger as BLN works 100% perfect on stock rom with cf-root, the rom was based on cf-root b84 so I chanced it to downgrade it to cf-root b82 and bam BLN fixed.
So the issue is down to a fubar kernel.
Now CM's stock rom doesnt support BLN, so on the CM roms I was using the blackhawk rom which has the exact same symptons as cf-root b84, seems only cf-root b82 works properly.
Here is the changelog for cf-root b83 and b84.
CF-Root-S5830-v3.7-b84.zip (12.55 MB)
BUGFIX: Invisible boot animation.
Install CF-Root-S5830-v3.7-b84.zip via "CWM recovery" first and then install b84-fixed.zip via "CWM Manager - Flash kernel"!
CF-Root-S5830-v3.7-b83.zip (12.38 MB)
- Untested since on CyanogenMod 7.2 firmware for now
- Using b82 recovery image
- CPU and system bus overclock enabled
- GPU driver backported from 2.6.35-11 kernel source
- interactive, interactiveX, smart*ss, and smart*ssV2 governor
- Samsung on the fly governor setting disabled
- WiFi driver taken from DXKPD
Click to expand...
Click to collapse
I dont have b83 but am about to flash mythICS which is based on b83, my gut guess is the bug was introduced in b83 as b84 only has a tiny changelog.
What I am asking is if someone can either do me a kernel for CM based on the above information (so dont include new GP driver, dont disable on the fly governor, dnt add new wifi driver) and see if the result is a fixed kernel, or if anyone has instructions on how to build my own kernel based on CM's sources.
I dont really need a new kernel for stock based roms as I can just downgrade to b82 cf-root to fix them.
Also is this better in dev section or here?
confirmed b83 is indeed borked and b82 also fixed on mythICS.
So I need a b82 for CM
Related
hi all!
Here s the story:
I went to flash VR 2.3 yesterday, which welcomed me with a blank screen at boot. Tried another rom, got same result.
A little scare and backup restore later, i was back on track and understood that those roms are KG3 based and a new kernel was not "recommanded" but NECESSARY
So, my question is this: if I update to KG3 Kernel, can I still run other stuff? If not, is it OK to flash an older kernel just for another older base rom?
Thanks!
EDIT:
[A]: Yes
Yes and no.
The actual kernel code itself has close to 0 changes from FW version to version.
(Though, there HAVE been some changes from 2.3.3 based ones to 2.3.4 ones).
Usually a 2.3.3 kernel works on most (if not all) 2.3.3 based FWs and same goes for 2.3.4.
However, there is more in the zImage than just the bare kernel code, there is the initial ram disk that takes care of booting up the OS.
Some ROMs depend on certain things to be or not to be in there (usually goes for custom kernels).
But there is really no problem just flashing a matching kernel for ROM/FW you're going to install.
Thanks a lot!
I just went ahead anyhow, and flashed KG3, then just let the phone reboot in VR 2.1 (which is KF2, I believe). it booted just fine, so I guess it might be, as you say, on a case by case basis.
I ll talk with VR dev so that he can edit the install instructions, which are a little misleading since he states this step is optional
Thanks for getting back to me!
Chroid flashes over your current kernel to an android kernel. This disables your overcloking in govnah. Govnah will not allow you to over clock. You will also not be able to flash a different kernel over it, even if you do remove chroid. So be forewarned. Only way to be able to change kernels is WebOS Doctor.
Have a safe pleasnt and positive day.
someone delete this ...click around dude this crap has been posted a million times already
only reason why the OP had problems is because he opened GOvna after installing chroid.
If you don't open govna, when you uninstall chroid ur OC kernel is restored.
The OC kernel can be restored however I noticed unusual high idle battery drain(about 15-20% overnight) with chdroid so I uninstalled it.
I apologize for restating that, even if it was posted everywhere.
p.s. I realized that it is possible to change the kernel if you first flash the stock kernel from preware then flash the kernel you'd like. It should work flawlessly
Help me, please. I just flashed my Optimus One with Goldenleaf kernel BFS v18c yesterday and it wasn't as good as it is reviewed by the users. It did not boost my performance, doesn't make my battery last longer, doesn't have a better gaming performance and what's worst is :
My camera stopped working.
Everytime I restart my phone, it asked me to force close setting.
It always doesn't read my sd card completely.
My gallery stopped working too.
I cannot connect my phone to the computer anymore. (it does nothing but only charge)
A black and white screen (like those in the television when you does not have signal) appears everytime i try to unlock.
The keyboard reacts vey slowly.
It doesn't auto rotate anymore. (Let's just say it doesn't rotate at all anymore.
So this morning i was trying to "un-flash" the kernel to the old stock kernel and flash it again with another kernel but couldn't find anything in the internet. I got angry and just flashed it with the new kernel (Goldenleaf BFS v18a) without "un-flashing" it first. I flashed it with Goldenleaf BFS v18a because i thought the older version might be more stable.
After i flashed it with Goldenleaf BFS v18a, the same thing still continue to happen.
I couldn't find anything in the internet. I don't know what to do, can anyone help me, please ?! Your help is very much appreciated.
When you flash a kernel different to the default rom, the only way to get back to that default rom kernel is to reflash the rom, in your case my best bet is your using cm7 6.5.8. That being said the latest updated franco kernel is cfs 19.2. Somethings wrong with the brain **** scheduler (bfs)..your best bet, reflash everything and start from scratch, do your backups than wipe everything in recovery, before I ever flash a rom or kernel..I always wipe cache and dalvik cache than flash than wipe cache/dalvik cache..the most important lesson is knowing a .32 kernel (goldenleaf, franco 19.2) are designed for .32 roms ,you can't mix a 35 kernel with 32 RIM or you'll end in a bootlop...read everything you can before you flash anything because those problems you say your experiencing I never once had myself.. don't expect gold, franco and fserve work there asses off trying to her good kernels out. To recap: either use fserves goldenleaf or francos cfs 19.2 but restart everything before you do, get a clean slate...inbox me if you got the same problems, alot of devs are tied up at the moment
Sent from my Optimus One using xda premium
Jrhodes85 said:
When you flash a kernel different to the default rom, the only way to get back to that default rom kernel is to reflash the rom, in your case my best bet is your using cm7 6.5.8. That being said the latest updated franco kernel is cfs 19.2. Somethings wrong with the brain **** scheduler (bfs)..your best bet, reflash everything and start from scratch, do your backups than wipe everything in recovery, before I ever flash a rom or kernel..I always wipe cache and dalvik cache than flash than wipe cache/dalvik cache..the most important lesson is knowing a .32 kernel (goldenleaf, franco 19.2) are designed for .32 roms ,you can't mix a 35 kernel with 32 RIM or you'll end in a bootlop...read everything you can before you flash anything because those problems you say your experiencing I never once had myself.. don't expect gold, franco and fserve work there asses off trying to her good kernels out. To recap: either use fserves goldenleaf or francos cfs 19.2 but restart everything before you do, get a clean slate...inbox me if you got the same problems, alot of devs are tied up at the moment
Sent from my Optimus One using xda premium
Click to expand...
Click to collapse
Can you show me a step by step tutorial? I'm really bad in this. I took 2 days to root my phone, that's how bad i am. And one more thing, it doesn't auto apply my Golauncher theme which i had moved to SD card when i turned it on and the keyboard reacts very slowly.
thanks for solving
Hi all...
Please could someone help me?
I am running the latest UK Sim Free ICS Stock ROM - and yesterday I updated the kernel as I wasn't best pleased with battery life.
Initially, I flashed Siyah 3.1.1 via Odin - and after initial boot up, "android upgrading" etc... I rebooted phone, went into recovery, and loaded the "Battery" profile.
The only other adjustment I made was turning off Auto-root and changed USB charging to 650mA in ExTweaks so that it charges via USB at the same speed as AC.
I made no other changes.
Then, the Siyah 3.1.2 Kernel was released, just a couple of hours after. So, I downloaded the CWM zip version this time, and also the Kernel cleaning script that is available on here (more for cleaning up the old stock kernel files than the Siyah)...
I rebooted into CWM and did the Update from zip - ran the Kernel cleaning script first, then flashed Siyah 3.1.2. I rebooted - let it do its "Android Upgrading" stuff and so on, then rebooted, loaded "Battery" profile, and made the same changes as originally - nothing more.
However, now, whenever phone reboots or powers on - I briefly get the "Android Upgrading" screen up for a few seconds. I didnt have this with the 3.1.1 - and am wondering how I can resolve this? I have definitely turned off Auto-Root, so it cant be this.
Another question, I recall reading, but cant find the post anywhere, that to disable the Siyah boot-animation that comes on just before the default Galaxy S2 one (in the same way a Carriers logo's does) - you need to create a file somewhere called .nobootanimation or something?
Does anybody know how to disable this so it just starts up like a stock S2 would? I love the kernel, but I personally prefer my phone to "appear" and feel as stock as possible.
Any help much appreciated - Thanks!
EDIT: I managed to find the post regarding the boot logo and have sorted that - but still found nothing on the Android Upgrading issue - Ive just reset ExTweaks profile through recovery options, no joy...
shadow2981 said:
Hi all...
Please could someone help me?
I am running the latest UK Sim Free ICS Stock ROM - and yesterday I updated the kernel as I wasn't best pleased with battery life.
Initially, I flashed Siyah 3.1.1 via Odin - and after initial boot up, "android upgrading" etc... I rebooted phone, went into recovery, and loaded the "Battery" profile.
The only other adjustment I made was turning off Auto-root and changed USB charging to 650mA in ExTweaks so that it charges via USB at the same speed as AC.
I made no other changes.
Then, the Siyah 3.1.2 Kernel was released, just a couple of hours after. So, I downloaded the CWM zip version this time, and also the Kernel cleaning script that is available on here (more for cleaning up the old stock kernel files than the Siyah)...
I rebooted into CWM and did the Update from zip - ran the Kernel cleaning script first, then flashed Siyah 3.1.2. I rebooted - let it do its "Android Upgrading" stuff and so on, then rebooted, loaded "Battery" profile, and made the same changes as originally - nothing more.
However, now, whenever phone reboots or powers on - I briefly get the "Android Upgrading" screen up for a few seconds. I didnt have this with the 3.1.1 - and am wondering how I can resolve this? I have definitely turned off Auto-Root, so it cant be this.
Another question, I recall reading, but cant find the post anywhere, that to disable the Siyah boot-animation that comes on just before the default Galaxy S2 one (in the same way a Carriers logo's does) - you need to create a file somewhere called .nobootanimation or something?
Does anybody know how to disable this so it just starts up like a stock S2 would? I love the kernel, but I personally prefer my phone to "appear" and feel as stock as possible.
Any help much appreciated - Thanks!
EDIT: I managed to find the post regarding the boot logo and have sorted that - but still found nothing on the Android Upgrading issue - Ive just reset ExTweaks profile through recovery options, no joy...
Click to expand...
Click to collapse
You would be better asking this question on the SiyahKernel thread
Thanks, I tried there first, and it said I couldnt post as i had less than 10 posts... :/
If this helps:
I re-flashed the 3.1.2 Kernel, this time via Odin (so no Kernel cleaning script run this time prior to flash), but I have the same problem.
I cleared dalvik cache afterwards, and as expected at first boot after clearing I get the:
Android Upgrading:
Optimising Applications
prompt.
Rebooted after this - but still get the:
Android Upgrading:
Starting Apps
at every bootup...
I tried "Fix Permissions" (even though I know this is not what it is for, on the off-chance)... but made no difference.
I reboot phone a lot - and whilst this doesnt effect the functionality of the phone, it does get quite irritating
As title suggests, there is a wierd (and Very annoying, since it forces me to use a while loop in a script to stick back to interactive) function in my kernel, which forces the CPU governor into ondemand every time screen-on/off occurs
Phone: Acer Liquid Glow E330
Kernel: all, this thing applies to stock, vache's, and lupohirp's kernel
PrintK says something about a str_governor variable (set to ondemand) which by circumstances gotta be the default governor
Any clues? Ideas?
Sent from my scytheaxe
SuicideFlasher said:
As title suggests, there is a wierd (and Very annoying, since it forces me to use a while loop in a script to stick back to interactive) function in my kernel, which forces the CPU governor into ondemand every time screen-on/off occurs
Phone: Acer Liquid Glow E330
Kernel: all, this thing applies to stock, vache's, and lupohirp's kernel
PrintK says something about a str_governor variable (set to ondemand) which by circumstances gotta be the default governor
Any clues? Ideas?
Sent from my scytheaxe
Click to expand...
Click to collapse
I never encounter such issue before, maybe you can change the kernal.
angelamar90 said:
I never encounter such issue before, maybe you can change the kernal.
Click to expand...
Click to collapse
Already tried vache's kernel and lupo's kernel, also tried to mod the stock boot.img to no avail. The issue is not in the ramdisk
Sent from my scytheaxe