Related
Good day everyone,
I have done my fair bit of reading in the past few months since I got my first android device (X10) when it launched (sold it 3 weeks later... lol) and since i have been browsing and reading posts after posts on diff. phones, after i had sold my X10 I was very interested in the EVO 4G due to screen size was on then verge of buying it, then I started working for Bell and the SGS came out, and I was sold.
So now I have an SGS i9000M, all this to bring you guys to my questions... general yet specific.
I started reading about roms/kernels/mods/etc... when I first got my SGS and took a dip and did my first flash with stock SGS Froyo 2.2 rom from another region, since it's still not out here from Bell (cell provider in Canada). when Bell UGJK3 came out, I jumped to that.. and finally, when Doc released UGJK3 1.x.. I said wth, let me go crazy and try one of them custom roms.
.... one word to describe it... WOW....
I was amazed at how smooth, fast, responsive the whole thing became. Needless to say I was hooked. Never would I go back to a Stock rom.
Now onto my question (if you're still reading, thank you)
I'm reading a lot about roms and kernels, so I did some research but I still have some unanswered questions.
1st) I read about a kernel K10x either 256 or 500, can someone tell me what that kernel is oc'ing? I have very good pc knowledge but phone wise = 0, on pc when you oc,. you can either oc the bus speed or the multiplier, obviously it's not the multiplier, so by that logic it's the bus speed, if default is 256, means multiplier is 4, since cpu is 1ghz, but then if it's oc'd to 500, means we're running a cpu at 2ghz?
Please someone clarify and clear that confusion for me....
2-A) I'm using Doc's 1.x for Bell because of the MODEM and CSC, I wanna try diff Doc's roms, like v9 or even other roms altogether, like ultimate etc...
Can I use flash any rom, and then with Odin flash, the modem and CSC file from Bell's UGJK3? will is break the rom? or would it still function perfectly but would have the proper APN once I change the CSC in the menu to BMC and allow for the proper frequencies usage (such as 850)... which brings me to part B of question 2...
2-B) I know when you change the CSC or do a hard reset everything gets flushed/wiped, if i have a custom rom installed and do that (a hard reset or change CSC) will the rom still work the way it was originally but with the added software/bloatware from the CSC, meaning will it still be optimized, snappy, and everything else that goes with it, or does it revert it back to "stock" rom, would I lose say my zipalignement or would the rom become odexed etc...
3) Regarding custom Roms, is it OK to flash say Ultimate 3.0, and then flash YA-OK Kernel? so that the rom would use that kernel if for me I find it runs better that way (regardless if Ultimate uses YA-OK to start with, it's just an example), or say Doc 1.3 Bell, using XXX Kernel. is there any incompatibilities, does a Kernel have to be modified to work with a specific rom etc... Also if say it's possible, do I flash the rom first and then Kernel, or vice versa.
If you're still with me, I appreciate your patience and if you take the time to answer, you have my kind regards.
Thank you in advance,
Rodi
bump
no one can answer these q's?
You would be well off to learn a bit about forum searching. Don't expect others to do your research for you.
1> -256, -500 indicate the 'refresh rate' of the kernel. It's a rate in hz, and doesn't represent an "overclock" at all and has nothing to do with the cpu. Some people find 500hz slightly more smooth/responsive, and may have slightly worse battery life. There's lots to read on this topic if you actually care.
2> I have used my i9000m on several modem and rom versions; it depends on the specific rom if it will be compatible with the Canadian market i9000ms; most should be with no problems, and the stock JPx roms/modems have worked fine for many. You can even use a JPx modem and still maintain 850mhz if you change the settings in the *#2263# Band Selection menu.
Note: I personally would stay away from odin with these phones, as there seems to be some kind of sd corruption (I've had to get a phone repaired, as have many others). Stick with 2e/CWM.
2-B> A factory reset takes your phone to the base firmware state. If you're using a full firmware rom, it should revert back to the options in said firmware. The CSC only specifies extras afaik, and shouldn't override any of the rom's base settings.
3> As long as the kernel is compatible with your current config, it'll work fine. I run Doc's Barebone UGJK3 w/ UGJK4 modem and k10i kernel. The only thing you probably need to be warry of is lagfix and advanced option compatability between kernels. If you disabled advanced options/lagfixes first, most other kernels will probably install just fine. Flash the base rom first, then everything you want to override (e.g. kernel/lockscreen/skins) after.
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.
=======
Originally Posted by evrionis View Post
I have a stock captivate rogers ROM and just installed the speedmon kernel and wish to install a modem since my bluetooth does not work well.
Bluetooth will never work properly when combining a Captivate-base ROM (like Cognition) with an i9000-base kernel (like speedmod). You'll have to switch to a different ROM to get bluetooth voice with that kernel.
Stock Cognition modem is JL1.
=======
So I've been doing research into fixing my bluetooth voice calling static issue. I'm running stock Rogers 2.2 on my I896 Captivate from Rogers. I've installed the latest speedmod kernel. As a result of some posts which claimed I needed to match my modem to my kernel I've tried a number of different modems in attempts to get rid of the static yet had no luck.
Is what this user posted above true, there is no combination of modem + speedmodkernel + stock rogers rom, that will fix the bluetooth voice static issue?
After each modem attempt I deleted my bluetooth profile on my phone and reconnected and still no luck. One user mentioned having to do a system reset on my phone after each modem as just deleting the bluetooth profile is not enough...can anyone confirm that? And what kind of reset would that be, key sequence?
Thanks so very much for any information!!!
Cheers
J
grasshands said:
=======
Originally Posted by evrionis View Post
I have a stock captivate rogers ROM and just installed the speedmon kernel and wish to install a modem since my bluetooth does not work well.
Bluetooth will never work properly when combining a Captivate-base ROM (like Cognition) with an i9000-base kernel (like speedmod). You'll have to switch to a different ROM to get bluetooth voice with that kernel.
Stock Cognition modem is JL1.
=======
So I've been doing research into fixing my bluetooth voice calling static issue. I'm running stock Rogers 2.2 on my I896 Captivate from Rogers. I've installed the latest speedmod kernel. As a result of some posts which claimed I needed to match my modem to my kernel I've tried a number of different modems in attempts to get rid of the static yet had no luck.
Is what this user posted above true, there is no combination of modem + speedmodkernel + stock rogers rom, that will fix the bluetooth voice static issue?
After each modem attempt I deleted my bluetooth profile on my phone and reconnected and still no luck. One user mentioned having to do a system reset on my phone after each modem as just deleting the bluetooth profile is not enough...can anyone confirm that? And what kind of reset would that be, key sequence?
Thanks so very much for any information!!!
Cheers
J
Click to expand...
Click to collapse
I was experiencing same kind of what you are experiencing now. Seems to be incompatibility issue while i'm on stock froyo and loaded speedmod kernel static is horrible (bluetooth) and during a call the other line have a hard time to understand what I have said. Tried clearing dalvik cache, factory reset, etc. only solution I had was to install a custom rom with speedmod kernel on it as the dev already tweaked it to be more compatible with the rom. So many roms out there it's up to you to choose. Once you have tried you may never think of going back to stock.
gorgy76 said:
So many roms out there it's up to you to choose. Once you have tried you may never think of going back to stock.
Click to expand...
Click to collapse
Well...that's the thing...I've tried pretty much all the popular roms and liked a few, but once rogers released 2.2 I flashed back to stock and use manual addons like speedmod/bln/lagfix/themes/batteryicon/etc. I feel I have more control this way and there seem to be less mysterious 'bugs' then when using cooked roms.
I've been keeping my eyes peeled for a fancy kernel based on the rogers stock kernel, but nothing has come about yet....
So at this point I'm still not clear if this is even possible, has anyone achieved running stock rogers 2.2 with a custom kernel and found some modem that doesn't cause an earfull of bluetooth static?
Thanks!
Cheers!
Ciao!
J
Try running the JK4 modem with the Speedmod Kernel. That always seemed to work out for me.
I am in the same boat ! Stock Froyo on I896 Rogers. I installed SpeedMod and got noisy bluetooth. Read a lot in here and flashed JK4 modem, still no go...
Everything is doing great ! SpeedMod with LagFix enabled is amazing ! But i need my bluetooth !!
Any Help would be great !!!
Thanks.
I tried and tried and eventually had to go on a long road trip and really wanted bluetooth to work...so I flashed CM7 and it's super nice and bluetooth works great! The only loss, IN MY OPINION, is that at the moment BLN is not included/working and only a couple people developing 3rd party kernels are looking into getting BLN back into a CM7 kernel.
CM7 is by default ext4 (so lagfixed out of the box!). And there are kernels for Voodoo sound/video/oc/uv.....just not BLN right now :/
So if you dont need BLN notifications, then give CM7 a shot!
Cheers
J
i search whole vivid forum about this problem
some guys (like me ) have problem with wifi on custom Roms
in some kernel wifi stuck on "wifi is turning on ..." and some kernel wifi could be on but it's crazy (like couldn't off) and couldn't find any wifi signal.
phone go to s-off but problem not solved
phone like Velocity 4G x710s
any body have a suggestion or help
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
mohamed_moscow said:
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
Click to expand...
Click to collapse
i found some "bcmdhd.ko" in some kernel
which is best for me
Cant wait for release!!
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes, upload that for us
Every kernel has it's own specific modules.
Thats why if you're S-ON you have to flash a CWM Zip and fastboot the img.
If you're S-OFF both are done in CWM.
This thread should be moved.
ok i find working file
tested with kozmik RC1 kernel and work well
Nottach said:
Cant wait for release!!
Click to expand...
Click to collapse
Hehe awesome.
I experienced the issue you described as a separate error from the common issue solved by a manual adb push for the wireless module.
Even though my phone is S-Off, I'd receive the error consistently when installing certain ROMs (but not all ROMs).
After multiple wipes (including formatting all SD drives, data and system partitions), I finally fixed the issue on my phone by fastboot flashing the kernel for the specific ROM I'm installing after doing a re-format/wipe and before starting the ROM installer through CWM.
It's a strange error, especially because everything seemed to be installed properly (including proper kernel info in the system) and my phone is S-Off, but this is the method I've found that works.
If anyone experiences the issue, I'd recommend doing a back-up, full wipe and re-format (including internal and external SD, basically everything you can wipe); and then fastboot flash the boot.img pulled from your ROM zip before going into CWM and installing (always be careful when fastboot flashing; if you're new to it, you definitely need to familiarize yourself and read a tutorial or two; don't blame me if you're new to flashing, don't read tutorials and end up accidentally flashing a kernel to the wrong partition or some other problem).
Hope this helps out some of the people experiencing this issue.
I can relate
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
daspazz said:
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
Click to expand...
Click to collapse
How did you get it working
Sent from my ADR6410LVW using xda premium
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.
Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...
snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?