Thanks the kernel development is awesome!!!
Hi,
I came from 6.03, which was working normally. After flashing 7.01- 7.03, my phone is consistently rebooting itself every 3 minutes or so. It boots up normally, and while it's on, everything seems to be going smoothly. I have tried Saurom RC3's prop.build to see if that would do anything since it doesn't have the tweaks that Iluminance has. This didn't do anything.
Then the screen freezes for a second or two and the phone reboots. Is anyone else experiencing this? Or is there anything I can toggle on/off to try and fix it? I tried turning off OC, init.d scripts, and BLN. I also tried all (including default and smartass) scaling governors.
I'm running Illuminance 3.0. I even wiped and reflashed with cwm and odin, but still got the reboots.
Thanks for mtcarey
Your work is awesome, Much appreciated.
I am on 7.03 (after a disaster with the 7.02 update). I have not had a reboot. Even better, I haven't had the sleep deaths I saw with other KK4 kernels.
Have you tried the standard trick of just reflashing the same file again?
What standard trick? Mines Ok so far.with fusion XII+corn kernel.
Sent from my SAMSUNG-SGH-I897 using xda premium
fixed???
I think I got it to work finally. I flashed Corn 6.03 after getting frustrated with 7.0x. Woke up yesterday with the idea that I should try 7.03 again with an idea. I converted all partitions to RFS with corn 6.03, then flashed 7.03. It worked all day flawlesses. Today I got brave and converted to EXT4 with Corn 7.03 and knock on wood it is still working really well. It's only been a couple hours but seems stable. I have it on SIO, Conservative, no OC, no BLN, stock voodoo color settings.
Cross fingers, maybe it is good......
Im on 7.03 ext4 and 1.2oc on 3 seperate devices and none reboot, all seem stable.
I tried 7.05 on all of em, and all of em rebooted during phone calls often.
Sent from my GT-I9000 using XDA App
7.03 worked from that day I posted. I went to 7.05 the day it came out and still working well here.
Hello, I dont think this is the right place to ask, but I couldn't find the right one, so sorry for offtopic.
On which ROMs can I use the Corn Kernel? Can I use it with CM/MIUI etc.?
The 7.x versions of the Corn Kernel are only for KK4-based ROMs. You can't use it with CM, MIUI, or any I-9000 based ROMs.
Related
I didn't know how else to title this thread, so I'm hoping this makes sense.
Awhile ago I flashed the CM6 ROM to my Hero. I haven't added much to it, nor adjusted any of the settings. However, when my phone is not plugged in and getting charged, when I hit the End Call or Menu button to bring it from sleep mode, it takes it almost 2 seconds before the lockscreen appears.
I know that a stock Hero will awake from sleep mode almost instantly. And, when I had a previous 1.5 ROM flashed, it took the phone about maybe 1.2 seconds to awake. Is this normal or is there something that I'm missing that is causing this lag? I haven't really installed any misc apps, and I only removed some "bloatware" from the phone (safely, and ones that don't cause FCs).
Any help or suggestions is appreciated.
I know that overclocking a rom adds lag to waking up the lock screen. Did you flash a overclocked kernel or have you had this issue since flashing this rom?
I believe, when I flashed this new ROM, I reverted back to a normal clocking speed. I used to have an OC kernel of 710, but could've sworn I've gotten it back to stock.
Is there a way to get it back to stock speed, if I didn't revert it back, tho?
Bump.
Is there a way to revert the kernel back to stock?
Option
1. If you have OC kernel install, either use setCPU or Overclock widget to set your min and max.
2. If you running ASOP rom, I'm not sure ASOP ROM comes with stock Kernel or OC Kernel. If it come with stock you may just flash the ROM again w/o wiping data, might have to wipe dalvik cache and it should revert back to stock kernel. If it comes with OC kernel, then option 1 would be best.
my .2 cent hope it helps.
Unfortunately, OverClock Widget didn't do anything to fix the problem. :/ And, if it can't fix it, I don't think that paying for SetCPU will fix it either.
Is there a way I can download the stock kernel?
You cab download setcpu for free here on xda or from their website
I forgot what file it is that changes the CPU speed, but I would look into modifying that file. I also have this problem with cm6 8/17 nightly, but did not have the problem with the early test releases
Sent from my HERO200 using XDA App
Thanks a lot, I'm giving it a shot now. I do have a question, tho: when I ran SetCPU, it said that root access was not detected. Is there a trick I have to do with the phone to have SetCPU recognize the phone? I have done some searching, but haven't found much. I tried checking on SuperUser, but it doesn't list SetCPU in it. Plus, when I tap on "Log", it crashes.
Is my phone messed up or something?
SO, earlier today Supercurio put together something special for those of us in Canada on the i896- a stock Rogers Froyo kernel with voodoo injected into it. Following logic, those of us on the stock Rogers Froyo should be able to have our cake and eat it too: a kernel modified especially from Froyo, intended for the Captivate, with voodoo lagfix but without the need to reflash an i9000modem or kernel. Here are the files:
Kernel: stock Rogers Froyo i896 w/ voodoo injection
Modem: Stock Rogers I896 UXJL1 Modem
Before trying a flash, I unlagfixed and backed up via Titanium Backup.
First I tried the kernel flash. I knew it wouldn't work with the modem, but I flashed it first to make sure there were no issues.
Rebooted into recovery- RED SCREEN
I did not enable the lagfix at this point. Just a straight reboot.
Regular boot screen; Rogers logo; Samsung Splash screen- then everything goes black. The home key buttons will light up and never go out if pressed. The phone stays like this until I pull the battery(I waited 25 min before I gave up).
I have tried various configurations regarding flash order(kernel/modem), I have repartitioned the card, factory reset before starting, everything I can think of, but this kernel won't boot past the splash screen.
However, when I revert to SpeedMod kernel(k13c) everything goes back to normal.
I would have thought I could flash this stock kernel over the i-9000 based kernel with the lagfix on both without issue, clearly I am wrong.
Can anyone see anything in my process that is inherently wrong, or even better would some other brave soul with stock Rogers Froyo be willing to try a flash? I wouldn't bother if this is your first crack at it though.
Thanks in advance to all who can help out.
So after wiping all caches and factory resetting, I get the following message at my Red Recovery screen:
E:Can't mount /dev/block/mmcblk1p2
(File Exists)
Is this important?
clemmie said:
So after wiping all caches and factory resetting, I get the following message at my Red Recovery screen:
E:Can't mount /dev/block/mmcblk1p2
(File Exists)
Is this important?
Click to expand...
Click to collapse
I get that all the time. No idea what the hell it is and have had to manually select my GSM bands when I flash a new rom or wipe dalvik cache since it started. Other then that no problems seem to be caused by it, for me.
Call off the dogs- after I installed the driver package that was included with Odin 1-Click I managed to get a master clear and a flash to the AT&T stock.
I must have spent 3 hours installing different driver packages today.
A shame it didnt work out smoothly. I'd be interested but am far too new to risk the troubleshooting..
Sent from my SAMSUNG-SGH-I896 using XDA App
Well, I have some very good news. This little kernel seems to be pretty special. After getting myself back to Rogers Froyo, I have done a few tests. I am getting very solid Linpack scores of 15-16 mflops and Quadrant Standard scores of 1400-1500. Using CPU benchmark, we have scores of about 725 ms @ 1000 hz and 700 ms @ 550 hz.
These scores are very solid and are about 20-25% improvement over stock Rogers Froyo Kernel.
This is promising as the kernel is a native Captivate kernel and could do a better job of servicing the many Froyo ROMs out there in terms of simplicity and stability.
The stock modem still needs more testing in terms of gps fixes and accuracy and data speeds.
I'll get back to you about those shortly.
If you have thought about staying on Rogers Froyo, this would be a good start for improvement.
clemmie said:
Well, I have some very good news. This little kernel seems to be pretty special. After getting myself back to Rogers Froyo, I have done a few tests. I am getting very solid Linpack scores of 15-16 mflops and Quadrant Standard scores of 1400-1500. Using CPU benchmark, we have scores of about 725 ms @ 1000 hz and 700 ms @ 550 hz.
These scores are very solid and are about 20-25% improvement over stock Rogers Froyo Kernel.
This is promising as the kernel is a native Captivate kernel and could do a better job of servicing the many Froyo ROMs out there in terms of simplicity and stability.
The stock modem still needs more testing in terms of gps fixes and accuracy and data speeds.
I'll get back to you about those shortly.
If you have thought about staying on Rogers Froyo, this would be a good start for improvement.
Click to expand...
Click to collapse
I would highly recommend this Kernel!! All the above benefits, plus fantastic battery life. The stock modem seems fine, although I've had better data transfer speeds and GPS locks from JL1 kernel, but this stock modem is perfectly fine.
Would love to see anyone else's results as well!
I like what I see so far. I am getting 1575 scores on quadrant (I know it doesn't mean much) but overall lag is gone.
I was a little freaked out this morning as the Rogers network was dead here this morning and I thought maybe I had done something with all this to kill cell / data. But everything cleared up after a few hours and I was back to normal.
Outcast, were you able to flash this custom Kernel without the issues that Clemmie came across? Much like phrenicthenub, I'd love to see the performance increase without the current bugs of custom ROMs, but I don't think I'm competent enough to troubleshoot if it all goes to hell.
As long as you disable any lagfixes and return any O/C or U/V kernels to normal you won't have these issues. Everything should work fine.
Sent from my SAMSUNG-SGH-I896 using XDA App
Did you guys do the 3e recovery fix first before being able to install CWM?
Hi guys... So i was trying to get SpeedMod to work with a i9000 modem like JK4, but my bluetooth is always noisy...
Right now, i have:
Latest SpeedMod kernel with LagFix enabled
JK4 Modem flashed.
What do i have to do to get this Rogers Supercirio's Voodoo kernel and modem ?
Thanks.
Elisha, I just took the plunge and got these flashed. Definately do the e3 recovery fix before setting up clockwork or anything else. That was the one part that gave me any trouble, but as soon as I got that sorted, everything went very well.
I'll try to pay attention to how things seem to perform and post my findings. Thanks for the encouragement again, Clemmie.
TheGrub said:
Hi guys... So i was trying to get SpeedMod to work with a i9000 modem like JK4, but my bluetooth is always noisy...
Right now, i have:
Latest SpeedMod kernel with LagFix enabled
JK4 Modem flashed.
What do i have to do to get this Rogers Supercirio's Voodoo kernel and modem ?
Thanks.
Click to expand...
Click to collapse
First you will need to boot into recovery and disable your lagfix. Back everything up with Titanium Backup. Download the files above to your root folder and reboot into recovery again. Using cwm, use the install zips option and flash both the kernel and the modem. Reboot yet again into recovery, clear your caches, then enable the new lagfix in your cwm options. It will take a while to convert your partitions from rfs to ext4, so be patient.
Sent from my SAMSUNG-SGH-I896 using XDA App
Thanks Clemmie,
I disabled LagFix from cwm and the speedmod kernel, rebooted, flashed modem with original JL1 modem, and then reflashed kernel with stock rogers froyo. backed everything up with Titanium backup. So i am currently back to stock, with a backup.
cwm is not in my recovery menu now, so if i use ODIN to flash the .tar version of supercurio's stock+voodoo kernel, does it contain cwm ?
ODIN with this kernel should work and then enable lagfix on first reboot by converting to ext4 right ?
Thanks alot, i am just starting with all this and want to make sure i understand everything before i take the plunge.
Thanks.
TheGrub said:
cwm is not in my recovery menu now, so if i use ODIN to flash the .tar version of supercurio's stock+voodoo kernel, does it contain cwm ?
Click to expand...
Click to collapse
Correct, it does.
TheGrub said:
ODIN with this kernel should work and then enable lagfix on first reboot by converting to ext4 right ?
Click to expand...
Click to collapse
Also correct.
Sent from my SAMSUNG-SGH-I896 using XDA App
Thanks ! i'll try that a little later... i'll let you know how it goes...
Well, so far, this Kernel seems to be the best thing to ever happen. I consistently get a score of 1501 in Quadrant standard (not from a fresh boot or anything, and running beautiful widgets and things, so I don't know if that makes a difference. I know with most benchmarks you're meant to close as much as possible, etc) and things just seem to be nice and smooth overall. On top of that, the battery life is, all of a sudden, seemingly PHENOMENAL! All whilst using the stock ROM. Either one of those benefits alone would have made the flash worth it. This is the way this thing should have run from the beginning.
I'll test out how well the GPS works, and try to pay attention to my signal strength with WIFI and calls and report back.
Thanks I figured as much as I had to do the 3e fix after I accidentally upgraded to the official Rogers Froyo the first day I got the phone.
Shroff said:
Elisha, I just took the plunge and got these flashed. Definately do the e3 recovery fix before setting up clockwork or anything else. That was the one part that gave me any trouble, but as soon as I got that sorted, everything went very well.
I'll try to pay attention to how things seem to perform and post my findings. Thanks for the encouragement again, Clemmie.
Click to expand...
Click to collapse
Ok, so i have used the tar version with ODIN3 v1.52 to flash stock+Voodoo-Froyo-I896-UXJL1. As i said, i was on stock kernel with stock JL1 modem.
Flash went great, took about 5 seconds, then rebooted. First reboot took about 7 or 8 minutes with a robot voice telling me the different steps it was in...
Everything workd without hickups... This kernel works realy well and speed is definitely there !
Thanks for the help guys...
Hi guys
I've been messing around with jvb, jvh, jvo and now jvp for a little while now, when flashing a fresh jvp the other day I had my 1st ever error in odin and my phone had a blue screen. I pulled battery and started again. I think my usb has been playing up on my laptop. So I got back into download mode and redid the flash but started with eclair, then froyo then back to jvp hoping to clear out any errors. Since then I had ramads deodexed jvp running great with hardcores kernel. I had flashed several of his kernels as he updated quite frequently. I then stated having issues with wifi toggle. Id click it on and it would flicker on and off. Then just stay off, so id click it again and same thing. Eventually it would either turn on and work fine or it will reboot my phone. Since then I have tried other kernels and it still does it whether its a fresh copy of jvp or just roms flashed over the top. So far I think with just ramads jvp it is ok but I havent tested enough. I remember reading on gto's forum about doing a full clean from eclair using 3 files and repartition but I can't find 2.1 or 2.2.1 with 3 files. I also remember reading about wifi errors and driver fixes but I can't find that any where. Can anyone help. Links to other posts or links to 3 file 2.1 & 2.2.1. also if I wanted to go back to froyo can I use froyo bootaders after having gb bootloaders. If so how would I do it. Thanks garth
Sent from my GT-I9000 using XDA Premium App
I've found that turning wifi off then trying to turn it back on straight after causes the reboots, i also found that stock jvp not Ramads jvp doesn't flicker at all. Just turns on ok. So it maybe root or cwm causing wifi to flicker. But battery life is terrible on stock jvp. So far browsing the net for no more than 30 mins on hsdpa, installing a few apps and battery died in 5hrs. Also went back to froyo 2.2.1 and wifi worked great. Then added hardcores kernel k13e and a cooked Rom but had many force closes even after wiping everything. Not sure what else to do, maybe root phone again, add all the goodies i like and just deal with wifi paying up sometimes, hoping to get a sgs II soon anyways
Sent from my GT-I9000 using XDA Premium App
The default from for the new rc3 release doesn't work on my phone, constant reeboots and freezes, so I'm wondering what other kernels are compatible with it. Currently I'm using the v52 kernel by grooby(?) But is giving me occasional reboots for no apparent reason.
hettar said:
The default from for the new rc3 release doesn't work on my phone, constant reeboots and freezes, so I'm wondering what other kernels are compatible with it. Currently I'm using the v52 kernel by grooby(?) But is giving me occasional reboots for no apparent reason.
Click to expand...
Click to collapse
I had the same problem, rc3 with the onecosmic kernel did not work, I installed the fugumod kernel, works fine for me.
hettar said:
The default from for the new rc3 release doesn't work on my phone, constant reeboots and freezes, so I'm wondering what other kernels are compatible with it. Currently I'm using the v52 kernel by grooby(?) But is giving me occasional reboots for no apparent reason.
Click to expand...
Click to collapse
you need no other kernel. Just flash RC3 over your current installation. I had these freezes and reboots too. after flashing RC3 and wiping cache/dalvik-cache about 4 times ICS seems to running stable and fast now.
Give it a try
I tried it many times, about a dozen or so. I don't think my phone likes the lower voltages the kernel uses by default. It only booted one in three times and when it did boot it never let me finish the setup screens before freezing.
@ regarding the fugumod one does flashing that one reintroduce the media storage bug? That was driving me crazy
hettar said:
I tried it many times, about a dozen or so. I don't think my phone likes the lower voltages the kernel uses by default. It only booted one in three times and when it did boot it never let me finish the setup screens before freezing.
@ regarding the fugumod one does flashing that one reintroduce the media storage bug? That was driving me crazy
Click to expand...
Click to collapse
I'm sorry that this didn't worked for you.
The media storage bug is still there even with the platypus kernel. So I think it's not kernel related.
Ahh thanks, I hadn't seen the bug since upgrading, but I don't think I had rebooted the phone since I got a working install. I tried a reboot just now and the problem showed up. Think I'll give the fugumod kernel a try.
This one is bugging me, because I can't figure out what is going on with this ROM on my captivate all of a sudden.
I've incremented through SlimICS 4.2, then SlimBean 2.0, then 2.1 and it was working fine. I figured 2.3 would be okay to go to to see if it helps further with speed/stability, but what is happening now is after it powers on, it works fine until the screen turns off. after that, I can't get any response from the phone, either by plugging in power, USB to Windows PC anything. I know it's still on because it runs warm, like some process has "run away" and I've even gotten some notification sounds from it, when the speaker volume was up. I've also tried re-flashing older 2.1, 2.0, SlimICS 4.2, but all versions of SlimRom have the same behavior. I thought maybe some file was not updating, so I downloaded CM10 (one off XDA with Devil Kernel), and that worked fine to turn off and on the screen. I was hoping I had overwritten whichever file is bad on Slim, and then re-flashed Slim, and the same behavior is occurring on all the Slim versions I've tested again. I prefer the toggle options of Slim, but would go CM10 if it's the only way. can anyone suggest anything regarding fixing an issue with the system not waking from sleep like this?
I know that in Recovery, the Power button works fine for presses, so the button itself is fine. Any help would be appreciated.
Thank you,
CaretakerThe
caretakerthe said:
This one is bugging me, because I can't figure out what is going on with this ROM on my captivate all of a sudden.
I've incremented through SlimICS 4.2, then SlimBean 2.0, then 2.1 and it was working fine. I figured 2.3 would be okay to go to to see if it helps further with speed/stability, but what is happening now is after it powers on, it works fine until the screen turns off. after that, I can't get any response from the phone, either by plugging in power, USB to Windows PC anything. I know it's still on because it runs warm, like some process has "run away" and I've even gotten some notification sounds from it, when the speaker volume was up. I've also tried re-flashing older 2.1, 2.0, SlimICS 4.2, but all versions of SlimRom have the same behavior. I thought maybe some file was not updating, so I downloaded CM10 (one off XDA with Devil Kernel), and that worked fine to turn off and on the screen. I was hoping I had overwritten whichever file is bad on Slim, and then re-flashed Slim, and the same behavior is occurring on all the Slim versions I've tested again. I prefer the toggle options of Slim, but would go CM10 if it's the only way. can anyone suggest anything regarding fixing an issue with the system not waking from sleep like this?
I know that in Recovery, the Power button works fine for presses, so the button itself is fine. Any help would be appreciated.
Thank you,
CaretakerThe
Click to expand...
Click to collapse
You could try flashing a devil kernel on top of Slim and see if that doesn't fix your problems. Typically when someone is having this sleep issue it's a result of enabling Deep idle in the kernel settings. But being that it's happening to you even after a clean flash I don't know if thats it. But considering that when you're on CM10 you don't have issues and when you go back to Slim, which is all Semaphore you have the issues I would say it's kernel related.
m1batt1 said:
You could try flashing a devil kernel on top of Slim and see if that doesn't fix your problems. Typically when someone is having this sleep issue it's a result of enabling Deep idle in the kernel settings. But being that it's happening to you even after a clean flash I don't know if thats it. But considering that when you're on CM10 you don't have issues and when you go back to Slim, which is all Semaphore you have the issues I would say it's kernel related.
Click to expand...
Click to collapse
Thank you Cappy m1batt1, that worked. I did have a Devil Kernel on my SD from a download link I found, and flashed that, it is working now. I have a Semaphore Manager app that came in the SlimRom, presumably with Semaphore Kernel. I found one for Devil Kernel from the Play Store just now. With any luck, I will not have to change or reinstall ROMs again before I can get a new phone...whenever that may be.
I would call this one resolved