Database Develop

cant connect to wifi at all

i cant connect to the wifi at all
was running cm6.1 was having problem
flashed back to FRG33. Everything works
except for wifi
when i turn on i get
application settings(inprocess com.androd.settings) is not responding then gives me force close

Seems something is corrupted...did you wipe when flashing?
Also try to update the Radio version...You could also try on FRG83 instead of 33 but that shouldn't make much of a difference, worth a try though

Wifi is generally managed by driver modules that are a part of the kernel. Perhaps try flashing a different kernel?

I quite often flash new kernels and I noticed that often a kernel may contain a new Wifi driver, if Wifi was turned on before flasing new kernel, afterwards Wifi may not be able to enable.
So when I flash a new kernel, I always turn off every communication features, 2g, gps off, bluetooth off, wifi off (although not all of them are necessary to be turned off ), then flash new kernel and wipe cache. It always works for me.
Since you're using CM so try this kernel:
http://droidbasement.com/db-blog/
before flashing it, turn off wifi, then goto recovery and flash the kernel and clear cache.
If you would like to save more battery you might like to try IntersectRaven or Wildmonk's AVS kernels, they are both compatible with CM.

thanks for all the help but i just go ahead and flashed back to FRG33
and when i tried to flashed to FRG 83 i failed to do it so
tried it in clockwork recovery
signature verifcation off.
then now i am getting an diff error and im assuming its becuase i have
higher version oh Hbooter?
i am going back to stock completely and try gingerbread when it comes out
so any help going FRG 33 TO FRG83?
should i just try and use the force update? and see if it works?
or do i have to do it manually if so any help would b appeciated.
for some reason cant flash to frg83. i named them as update.zip as well
is it suppose to be 80 mb file? dont i just need an OTA update file?
well in wiki the file that told to b used was 80mb file
if so where can i download proper OTA file
tried to find it but most of the links are corruped it or does not exist anymore
and the one on the wiki is to confusing. there was one update that goes ef something to FRG83 but i couldnt flash it cause i had higer hboot version. downgrading is too confusing for me.
right now i have 2.2
basebandversion 32.41.00.32U_5.08.00.04
kernel version 2.6.32.9-27237-gbe746fb
[email protected]#1
build number frg 33
i want to get 2.2.1 (FRG83) idk which kernal works best for wifi..when i wiped out everything and reflashed it it worked for 3min then got disconnected and now im getting the same forceclose
i know i have lots of question sorry.

why sticking with official roms there are bunches of excellent roms in Development section. All roms should already contain a kernel which works for that rom, so just carefully follow instructions and flash a new rom, see if wifi works.
I'm currently running CM 6.1 RC1.
http://forum.xda-developers.com/showthread.php?t=722798

[I9000M] JL2 + SpeedMod kernel - results?

In an effort to get BLN back on my I9000M, I'm trying to decide if it's worth switching to the SpeedMod kernel. Since I've got my I9000M back from repair and upgraded to JL2 it's been running flawlessly so I don't want to mess with it - but I do want BLN.
So JL2 users with SpeedMod - any problems so far? (and which version of SpeedMod are you using?)
I'm referring to this SpeedMod, btw:
http://forum.xda-developers.com/showthread.php?t=822756

I would definitely switch to SpeedMod. It's a great, fast kernel with a ton of options.
It wouldn't cause the SD card to die, if that's what you're thinking, because by flashing the JL2 firmware you're flashing the secondary boot loader (Sbl.bin) which fixes the issues with the SD card. The kernel is like an entirely separate entity than the sbl, which means it won't brick.
So, go ahead and flash it.

Thanks for the feedback. I wasn't worried so much about the internal SD as I was about things like WiFi battery drain which seems to have become an issue in some of the 2.2.1 releases.
But since I'm not too familiar with Android/Linux development, I'm don't know if it has more to do with the JP* firmwares or the kernel itself.

I've been running it with speedmod k10k all lagfix/speed options disabled (I don't need them, this rom is quick!) and my phone is working like a champ. wifi/gps off, push/pull on w/ hsdpa, I can go just about two full days without charging. With wifi on and gps on plus everything else, I can go about 10-12 hrs.

seeARMS said:
I would definitely switch to SpeedMod. It's a great, fast kernel with a ton of options.
It wouldn't cause the SD card to die, if that's what you're thinking, because by flashing the JL2 firmware you're flashing the secondary boot loader (Sbl.bin) which fixes the issues with the SD card. The kernel is like an entirely separate entity than the sbl, which means it won't brick.
So, go ahead and flash it.
Click to expand...
Click to collapse
I was under the impression that the sd card issue was a bit deeper than just flashing a new bootloader. Is there a thread with more about this? i dont want to brick any more phones, and if flashing JL2 will correct the memory issues, i'll gladly go back from jpy. and is there any way to flash the SBL (if it in fact fixes the sd corruption) without changing anything else? ie: sticking with my jpy without a whole pile of flashing to jl2, then back, etc.

Thanks for the input. Running now with all the recommended tweaks but no lag fix... Maybe a bit more fluid in the ui, but honestly jl2 was so fast to begin with its hard to tell All i really care about is that i got bln back.
Will be watching battery overnight with fingers crossed.
Sent from my GT-I9000M

pervert said:
I was under the impression that the sd card issue was a bit deeper than just flashing a new bootloader. Is there a thread with more about this? i dont want to brick any more phones, and if flashing JL2 will correct the memory issues, i'll gladly go back from jpy. and is there any way to flash the SBL (if it in fact fixes the sd corruption) without changing anything else? ie: sticking with my jpy without a whole pile of flashing to jl2, then back, etc.
Click to expand...
Click to collapse
I too would like a little more official information about this, and whether the new SBL fixes this. As this seems a little to quick for Samsung to say they've fixed the problem. Who knows that would be a great not to live in fear each and everyday I use my SGS

I'm so new to this - is this easy to do ? to flash this rom ?
where's the best way to start, you tube? is there any reccomended tutorials ?

I have a SGS from bell, it's my 2nd one. I haven't upgraded to Froyo yet b/c I can't connect to Kies. Should I just flash instead ?

radeon_x said:
In an effort to get BLN back on my I9000M, I'm trying to decide if it's worth switching to the SpeedMod kernel. Since I've got my I9000M back from repair and upgraded to JL2 it's been running flawlessly so I don't want to mess with it - but I do want BLN.
So JL2 users with SpeedMod - any problems so far? (and which version of SpeedMod are you using?)
I'm referring to this SpeedMod, btw:
http://forum.xda-developers.com/showthread.php?t=822756
Click to expand...
Click to collapse
Running JL2 + Speedmod + lagfix, phone is fine so far. BLN was causing the touch aspect of my screen to not work so i couldnt even unlock it. havent had a change to fool around with it though.

Been running Super Optimized Kernel instead of SpeedMod in my custom ROM, and I've noticed that its been much faster. Gonna stick with it for now.

[Q] Boot Loop when installing ROM

Hey guys; i'll try to provide you with all the information but honestly i'm not 100% on all of it so try and be patient.
I'm trying to go back to SuperE from Froyo by Laszlo which was absolutely killing my battery without me even using it. However, every time i flash it (and i wipe everything) after it goes past the G1 screen it just resets again.
I'm not sure if this is maybe because of the new kernel (2708) which i'm PRETTY sure i have, but am not 100%. I do know that i have one of the new radios though.
Would the kernel be causing the problem? If so how do i downgrade?
I hope you can help me out!
Thank you!

Q: Can you mention step-by-step what did you flash? And confirm the exact setup before flashing. I believe you mentioned your radio is 2708.
Powered by Android

Thank you for replying. I'll definitely try.
I'm back on FroyoByLaszlo-int2.1 because i couldn't successfully flash either Super D or Super E.
My Radio is 2.22.28.25
Kernel version says 2.6.35.10 - froyobylaszlo
Basically i did what i always do. I wiped everything, first by flashing the "all-wipe" and then going back and wiping it all manually.
Then i flashed the appropriate gapps, followed by the ROM. Rebooted afterwards, but every time it gets passed the G1 screen it reboots.
The only thing i can think of is incompatibility with the kernel but then again, i don't know crap, so that's why i'm asking

Yep, most likely it is indeed the incompatibility of the kernel with the radio.
I'd try flashing the ezBiffTestKernel20101106-2708.zip after the ROM+GApps.
Just use Google to find the kernel.
Powered by Android

The battery drain could be becos of the new kernel. Try installing the 35.9 kernel from ezterry (the one he had for CyanogenMod 6.1 2708) It is working good for me, the battery last for a whole day.

[Q] Ok to use modded kernel with stock froyo (KB1)?

Is it ok to use a modded kernel (like paragon) with a stock rom (KB1)?

I believe so.i think as long as you use a 2.2 kernal. I'm probably wrong though. Lol
I kill coneys, not phones.

The various release notes imply that it is possible but since its my wife's phone I dont really feel like getting killed for bricking it.

kevria said:
The various release notes imply that it is possible but since its my wife's phone I dont really feel like getting killed for bricking it.
Click to expand...
Click to collapse
Have no fear. If you follow the instructions you will be totally impressed with the performance improvement. I am running totally stock with the exception of my stock kernel with voodoo lagfix and you can't beat it with a stick.

clemmie said:
Have no fear. If you follow the instructions you will be totally impressed with the performance improvement. I am running totally stock with the exception of my stock kernel with voodoo lagfix and you can't beat it with a stick.
Click to expand...
Click to collapse
Which kernel are you running?
Edit: Nevermind, just read your sig file.

Cognition 4.x is basically stock Froyo with a lagfixed kernel.

If you don't want to venture too far from stock, you could use Supercurio's stock + Voodoo lagfix kernel for KB1.
http://forum.xda-developers.com/showthread.php?t=870760
You can flash the CWM version using SGS Kernel Flasher. It'll take a while for the first boot up, but you'll get audio prompts that it is working. Just take your typical precautions...backup, blah blah blah.
Works great with KB1.

lactardjosh said:
If you don't want to venture too far from stock, you could use Supercurio's stock + Voodoo lagfix kernel for KB1.
http://forum.xda-developers.com/showthread.php?t=870760
You can flash the CWM version using SGS Kernel Flasher. It'll take a while for the first boot up, but you'll get audio prompts that it is working. Just take your typical precautions...backup, blah blah blah.
Works great with KB1.
Click to expand...
Click to collapse
I actually have CWM flashed onto her phone from installing PlumbBob's GPS fix so I could flash it with CWM. Thanks.
My main reason for flashing a different kernel was because her battery life is lousy compared to my phone with Serendipity and Paragon.

kevria said:
I actually have CWM flashed onto her phone from installing PlumbBob's GPS fix so I could flash it with CWM. Thanks.
My main reason for flashing a different kernel was because her battery life is lousy compared to my phone with Serendipity and Paragon.
Click to expand...
Click to collapse
IMHO, the battery life has been great since flashing that kernel. I haven't done any official logging or anything, though.
And the difference in speed because of the lag fix is unbelievable. Incomparable.

lactardjosh said:
IMHO, the battery life has been great since flashing that kernel. I haven't done any official logging or anything, though.
And the difference in speed because of the lag fix is unbelievable. Incomparable.
Click to expand...
Click to collapse
Great, thanks. I guess I know what Im doing this weekend.
Edit: Installing that Kernel didnt wipe your phone did it?

Voodoo+KB1 = Speed, Performance & Reliability
lactardjosh said:
If you don't want to venture too far from stock, you could use Supercurio's stock + Voodoo lagfix kernel for KB1.
http://forum.xda-developers.com/showthread.php?t=870760
You can flash the CWM version using SGS Kernel Flasher. It'll take a while for the first boot up, but you'll get audio prompts that it is working. Just take your typical precautions...backup, blah blah blah.
Works great with KB1.
Click to expand...
Click to collapse
I absolutely agree with you lactardjosh.
Suoercurio has done a fantastic job in creating these kernels.
I flashed the V+KB1 the other day and my devices runs as if it's on a silicon base. Smooth - Extremely responsive - No difference in battery life - and most importantly - All of the features that are supposed to work...do!
Peace-
Liv33viL

kevria said:
Great, thanks. I guess I know what Im doing this weekend.
Edit: Installing that Kernel didnt wipe your phone did it?
Click to expand...
Click to collapse
Flashing the kernel did not wipe my phone. BUT, you should definitely do a back up before flashing it. Just good practice.
The first time you boot up after flashing the kernel, it will take a while to finish booting. It'll stay on the AT&T World Phone splash for quite a while. You'll get a digitized voice telling you that the Voodoo lag fix is running and it'll give you an estimated time to complete it. The first time I did it, I couldn't understand what it said, but after messing up something else and having to go back to 2.1 and then upgrade to 2.2 again (which did wipe my phone), I realized that the first time it had told me it was going to take 10 minutes to enable the lag fix. The second time around, it took 2 minutes because there was nothing extra on the phone since it had just been wiped. So, depending on how many apps, etc, you have installed, the lag fix will take a more or less time. Let it run, find something else to distract you from how long it is taking.

I have enabled the lagfix on my phone. My wife has a LOT of apps on her phone so it will take awhile. I backed the rom up using rommanager and copied the Titanium backup directory off to my home computer.

I installed the Supercurio kernel last night on my wifes phone so it will be interesting to see whether the battery life gets any better. The phone should run smoother though.

kevria said:
I installed the Supercurio kernel last night on my wifes phone so it will be interesting to see whether the battery life gets any better. The phone should run smoother though.
Click to expand...
Click to collapse
My Captivate runs great on the KB1+Voodoo Kernel from SuperCurio!
The performance of this Kernel has actually kept me on the stock ROM (for now)

bobapunk said:
My Captivate runs great on the KB1+Voodoo Kernel from SuperCurio!
The performance of this Kernel has actually kept me on the stock ROM (for now)
Click to expand...
Click to collapse
I told my wife that her phone should be snappier now but the battery life may stay the same. Also told her to drain the battery down to nothing, charge to full while off, unplug and plug back in, wait until its full then unplug and turn it on.

[SOLVED] Flashing Kernels

Heya guys,
I've been flashing kernels on my phone using mobile odin and sometimes CWM.. I just want to make sure that this is safe? or is there a limit on the safe number of flashes or is there like a deadly combination?? (Example : currently on speedmod then flash hydracore then go to another different kernel then flash another totally different one)
I'm having second thoughts since i think that this might trigger a corruption with the kernel on the phone if the previous kernel was not fully deleted or cleaned or should i Flash stock kernel after a few number of flashes just to make sure the phone is properly cleaned? (i'm also aware of the brickbug so no worries )
I'm just on a stock 4.0.4 and been rooted primarily with notecore v14.1 std then ive been flashing like 30times already since then trying to look for a proper kernel for me..
Sooo, is there anything to watch out? like "dont flash this kernel if you're currently on this other kernel.. etc etc.."
Don't worry I'm always watching out if its stock touchwiz compatible and ICS compatible before i try a new kernel..
And maybe you might also ask, why am I doing this.. I have a problem with my phone that it totally loses signal to the point that the phone says "no service" and then it would reconnect after 1-2mins.. I've proven that its not a network issue since my other phone is sitting pretty on the same desk with no problems on that same cell network.
At first i thought this might be a modem related problem so I flashed multiple different basebands and finally settled with XXLRK since it gave me best data speeds.. So now I'm looking into the possiblity that my problem is kernel related.
Any ideas about this would also be appreciated :highfive:

Personally, I use siyah kernel cleaner first before I jump from one kernel to the other. I just find it's good to run the kernel cleaner first before you jump kernels. And to answer your question one at a time:
1. There is no limit on flashing kernels in your ROM, as long though as you have downloaded the kernel's size correctly. A corrupted or bad download on the kernel itself can cause your phone not to boot anymore. So be wary about it.
2. With regards to your "No service" issue, I don't think the issue is really kernel related. Bear in mind kernels are developed for the primary purpose on performance on CPU/governors and battery.. its one, the other or a combination of both. It's not even touching the radio band itself so I don't think this again is the source of your signal issue. A modem issue perhaps, but not the kernel.
Personally, I'm using LB1 as my modem, it's blazingly fast on the downloads. Had used LRK modem before but I found out that my data speed would randomly connect and disconnect my connection. Flash LB1 modem and it seemed it's all fine and dandy now.