Hi,
I'm using unlocked captivate with T-mobile.
I recently installed galnet MIUI for captivate, with GT-I9000 bootloader.
I was wondering, since i am on GT-I9000 bootloader, wouldn't every single one of stuff on my phone (kernel, moden, etc) should be I9000 version of it, for better performance?
right now i am on baseband version of I9000XXJVK
with i897 version of galnet miui stock kernel.
shouldn't i change my stock kernel to i9000 version of it, since bootloader is i9000?
thx in advance.
no, unless you want your rotation, sound, soft keys, elect messed up.
I897 and I9000 are similar not the same. Something work cross device like modems, and others require porting to work like roms and kernels
speedy_11 said:
no, unless you want your rotation, sound, soft keys, elect messed up.
I897 and I9000 are similar not the same. Something work cross device like modems, and others require porting to work like roms and kernels
Click to expand...
Click to collapse
thanks for the answer.
on more thing tho, what do you mean by requiring porting to work?
dskim0506 said:
one more thing tho, what do you mean by requiring porting to work?
Click to expand...
Click to collapse
Porting means modifying software to work on another platform, which can be either a different operating system, or different hardware. For instance, a software developer might be asked to port his windows program to mac or linux. This usually means rewriting or modifying the source code and then re-compiling the program. (This example would not be trivial, probably requiring almost a complete rewrite, lol.) In the case of I-9000 and I-897, there are some differences in the way the hardware is configured between the two phones, and that requires the software to be configured somewhat differently, mostly in the kernel, which is the software layer that most directly works with the hardware. Once the developer has access to the source code, then he rewrites those sections of code that relate to the hardware differences, and the software is re-compiled. So, software originally written to work with I-9000 hardware can then work correctly with the I-897.
still not working...
tried 3 times, and still not working.
in recovery mode, i wiped cache and dalvik cache, and then flashed talonMTD kernel for captivate
the phone still gets frozen after screen goes off
Thats weird. You did that from a fully functional miui install? I don't see why it would fail.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
T-T
xijar said:
Thats weird. You did that from a fully functional miui install? I don't see why it would fail.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'd say i did everything right.
well, i'm on galnet miui 1.8.12...
i followed this instruction:
http://www.galnetmiui.co.uk/content/forum/guides/(work-in-progress)-lttldvl's-clean-install-method/
doubt this makes any difference, because it didn't work when i flashed regular miui by following
http://miuicaptivate.weebly.com/install.html
after all these, i did format both cache and dalvik, then went to install from zip,
then flashed TalonMTD.
after that, I reboot, install setcpu, undervolt -100 for 1GHz and down,
turn the screen off, and the phone gets frozen after few seconds....
waahhhhhhhhh
Too much UV in the 100 mhz zone
Corrupted TalonMTD download
Does the TalonMTD work on Galnets MIUI?
Sent from my Cappy at 1.6 GHz, V6 supercharger, KAK tweaks, and 3G booster using the XDA Premium App!
Your phone should be on i897 bootloaders. The kernel should be tuned for the hardware (i897) and the bootloades need to be for the hardware as well (i897). The bootloaders are responsible for initializing the hardware and the kernel runs the hardware. Don't change your bootloaders...
Regardless of which Developer says "OMFG HEY RUNZORZ MY ROM CUZ IT'S GOOD" never change your bootloader. Those "Developers" are retarded.
Related
What is this? It's an experimental ROM install setup that avoids the use of RFS entirely. The install basically pre-voodoo's your phone. If you know you want voodoo, this is faster than installing then doing voodoo, but it's a little more complicated. Not much, but be warned. It avoids the use of RFS durring install completely, so no RFS corruption to worry about.
The ROM itself is mostly untouched. The kernel is my Dragon Kernel, i9k based, so it will eat your battery (froyo only, eclair is better as we have source). I can get about 12 hours out of it. Buy a charger.
The new version is a 1-click install. It installs the kernel, reboots into it, then auto-installs the ROM. I tested it coming from JFD without issues.
These are based on voodoo5 beta code. Curio is releasing voodoo5 stable here soon, and I'll post an updated no-wipe kernel flash for that.
The ROMS are Team Whiskey Obsidian, Onyx, and Fusion. I changed the install procedure and the kernel out, the rest is as they made it. I take no credit for the ROM. Please post bugs here however, so I can make sure they are ROM bugs before letting TW know about them. I'm running the Onyx version as my daily driver. There has been some private beta testing, and they seem stable, but do have Odin handy just in case. I have installed over the top of various ROMs, but the safest way is probably to come from JFD just to be sure.
ALL THESE ROMS WIPE. NO, I WON'T CHANGE THAT.
Obsidian V5b: http://www.tabbal.net/files/Dragon-Obsidian-Installer-v1.0.zip
Onyx 4.2: http://www.tabbal.net/files/Dragon-Onyx-Installer-v1.0.zip
Fusion Final: http://www.tabbal.net/files/Dragon-Fusion-Installer-v1.0.zip
NOTE: THESE INSTALL VOODOO. ALL THE USUAL VOODOO PRECAUTIONS APPLY, IF FLASHING SOMETHING, DISABLE IT FIRST.
The latest voodoo stuff seems to play nicer and I have flashed things from clockwork without bricking, but just be warned.
Updates:
Kernel with the stable voodoo5 release. Should work with any froyo ROM, does not wipe.
http://www.tabbal.net/files/Dragon-Kernel-Voodoo-v2.0.zip
I can conform that these are indeed working. And they work beautifully. I'm evening thinking about going back to some voodoo love.
Love your work ttabbal.
"if you amplify everything, nothing is heard"
Hmmm...cool. Might have to try this with Axura 2.1.
geoffcorey said:
I can conform that these are indeed working. And they work beautifully. I'm evening thinking about going back to some voodoo love.
Love your work ttabbal.
"if you amplify everything, nothing is heard"
Click to expand...
Click to collapse
Curious! So what's the true (RFS free) Quadrant score for Vibrant?
Can we have just a kernel flash that will convert all the partitions? supercurio's i9000 flash doesn't wipe the data, it simply tars it and then untars it back once the conversion is done to each partition. Thanks for the hard work.
dasunsrule32 said:
Can we have just a kernel flash that will convert all the partitions? supercurio's i9000 flash doesn't wipe the data, it simply tars it and then untars it back once the conversion is done to each partition. Thanks for the hard work.
Click to expand...
Click to collapse
The post is about the ROMs, but yes, the kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
It's the custom kernel I reference in the OP. If you want more than about 12 hours off charger, don't install it. I'm going to look at Eugene's recently posted source to see if I can implement whatever he did to get the kernel sleeping better, but no promises. And reports are kind of mixed last time I looked at it anyway.
When Samsung gets around to releasing source, we can do better. Till then, give me a patch or don't complain about it.
ttabbal said:
The kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
Click to expand...
Click to collapse
Nice. I'll hold off trying this with Axura 2.1 until this posted, then. A battery life of 12 hours is fine in exchange for what Voodoo will provide in return.
ttabbal said:
The post is about the ROMs, but yes, the kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
It's the custom kernel I reference in the OP. If you want more than about 12 hours off charger, don't install it. I'm going to look at Eugene's recently posted source to see if I can implement whatever he did to get the kernel sleeping better, but no promises. And reports are kind of mixed last time I looked at it anyway.
When Samsung gets around to releasing source, we can do better. Till then, give me a patch or don't complain about it.
Click to expand...
Click to collapse
Sweet, thank you.
i flashed this on obsidian v5 beta w/ jk6 modem and it running like a champ. however, you were right about the battery life
thanks for posting it before hand. i appreciated.
Love the new kernel would u consider an overlook version? Eugene 1256 is so snappy but it corrupts data. That speed plus voodoo is crazy fast. Real 2000 + quadrant.
Sent from my GT-I9000 using XDA App
Froyo Kernel on Eclair?
ttabbal,
I did not know that a Froyo kernel could be backward compatible to Eclair. Is that the case, given that your Dragon 2.0 incorporating Voodoo 5 Stable will work with Bionix Fusion?
Please help me to understand this.
More to the point, I am on Bionix 1.9.1. Would Dragon 2.0 w/Voodoo 5 Stable work on my setup?
Thanks,
Bruce
Would love to use this, however i cant seem to get anything to install from the market no matter what i do. My TitaniumBackup restores just fine(apps only). Ive ODIN'd back to JFD twice but still nada. Ill try starting from JI6 and see if it helps.
dbacchus said:
Curious! So what's the true (RFS free) Quadrant score for Vibrant?
Click to expand...
Click to collapse
So I'm running ttabbal's latest kernel, 2.0, and just ran a quadrant. It gets 1564 as the score. Now, this isn't just from voodoo alone, he's done a few speed tweaked which will bump up the score. But it's snappy as hell.
"if you amplify everything, nothing is heard"
Just put this in my phone and its works fine I'm running axura 2.1 works fine but u will see a second boot up screen the benchmark test is not that high I got in the 2500 with the oclf inthe market download but can't do that one anymore it tells me I have one installed already but over all its smooth
Don't worry about benchmarks, they are easy to fool in a high level system like Android. Cyanogen managed to get something stupid like 10k out of Quadrant.
This setup isn't for being a benchmark queen. It's targeted at a couple things I deem important. Multitasking smoothness/performance, and a test of direct-to-ext4 install. The no-wipe voodoo kernel is really intended to be used as part of the whole, but like I said, it should work with any froyo. Note: NOT ECLAIR. If there is more demand for an eclair version, I'll consider updating my eclair ramdisk as well.
As for the market, couldn't say. It's NOT the rom/kernel though. The market is a finicky thing and sometimes just doesn't work. It's usually the server side or the app itself that has an issue though. There's also an update to Market for Froyo, it seems to be more stable. You should get it downloaded automatically after running for a while. To check, look at an app description, you should have a new tab "Related".
When I've had market problems, I fire up my Wife's G2 on a stock rom (not even root) and she does too, so it's not anything I, or anyone other than Google, can control.
Does anyone know whether the Dragon Kernel that works with any Froyo ROM available from the OP supports use of a BootAnimation.zip?
UPDATE: Thanks geoffcorey for the info!
Tried on Axura 2.1 with larger nand. Flashed, rebooted, converted with no issues and is running very well so far. Haven't been successful getting Voodoo to run before now.
Thanks to TW, ttabbal, Supercurio, et al.
epakrat75 said:
Does anyone know whether the Dragon Kernel that works with any Froyo ROM available from the OP supports use of a BootAnimation.zip?
Click to expand...
Click to collapse
yes, it supports bootanimation.zip
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Sent from my SGH-T959 using XDA App
joe.kerwin said:
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Click to expand...
Click to collapse
I did this very thing in my post #16 above yours. Go for it! Remove any other lag fixes you may have though. I had none installed so I didn't have to do that. PERFORM A NANDROID backup and optionally copy to a computer before flashing the kernel to be safe. Restoring the Nandroid backup won't restore the kernel though.
The dangers are minimal if you backup. Permanently bricking the phone is unlikely. You may soft brick but you probably won't. PLUG IN AND DON'T TURN OFF THE PHONE UNTIL THE "TW" LOGO DISAPPEARS! Around this time, you will hear a voice say voodoo has been activated.
I believe the conversion process may attempt to revert the changes it tried to make in the event of an unsuccessful conversion. If reversion is successful then you should again have access to CWM to flash back to any rom you have stored on your phone. Use nandroid to restore your data and your back to normal.
joe.kerwin said:
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Heimdall... Um if you cant get into download mode perhaps you shouldn't flash experimental things.
Sent from my SGH-T959 using XDA App
Hi there! I'm new to the forum and to android as well.
As you can guess I'm a proud owner of SGS
Since my SGS sucks a bit (random crashes, reboot, RFS) I'm interested in taking the maximum out of it, and I have some questions.
What is the difference between kernel and a rom? As far as I know from Linux and OS theory, kernel is the layer between the user (applications) and the hardware. I also know that most of the ROMs have kernel in them. Then what else the ROM contains?
What is firmware? Is it used a synonym for kernel/rom?
Is it worth installing custom kernel/rom on SGS? I'm a bit paranoid in those things and have some fears about the issue.
Is there a way to install some good kernel (like speedmod) and naked ROM (not someones mod, i.e. a stock android ROM without any additions from third party developers)? Is it hard to make my own ROM based on stock ROM (without touching the kernel, even tough I looked at the code and read books about the linux kernel, I dont yet consider my self a guru to be able to make my own kernel for android), just the modification and custom applications?
Thanks a lot guys!
Everyone has a kernel - even if you don't mod your phone at all. It wouldn't work without one!
Now, if you flash a ROM, you change the whole system including the kernel. If you flash a kernel, you're only changing the core piece of your system.
Sent from my GT-I9000 using XDA App
A rom is a full firmware .
A kernel is the bit at the base level between processors and OS .Or just as you said .
Is it worth installing custom kernel/rom on SGS? I'm a bit paranoid in those things and have some fears about the issue.
YES but its at your risk though SGS is relatively un brick able .
Simplest upgrade would be via Rom Kitchen and build your own rom .
Choose base rom kernel modem and CSC to suit plus themes and apps .
http://forum.xda-developers.com/showthread.php?t=817703
jje
The kernel in android is essentially just a customized Linux kernel. The ROM is basically the application layer and the framework. Usually ROMs include kernels, but you can flash a different compatible kernel.
Firmware usually refers to either all the basic software on your phone (minus the apps) or the ROM, csc and modem.
You can definetly flash a custom kernel onto a stock ROM, which will improve performance a great deal even without a custom ROM. Find instructions aplenty here on XDA.
Sent from my GT-I9000 using XDA Premium App
Thanks for the replies guys!
YES but its at your risk though SGS is relatively un brick able .
Click to expand...
Click to collapse
By un brick able you mean that its hard to brick it, or if I brick it its hard to un brick (fix) it then?
Also I'm having a hard understanding, if kernel is the thing that manages the hardware and also responsible for lagfix then kernel is really what matters for the performance of the phone. How a ROM could improve phones performance?
Also one more questions:
As I understand CSC and modem are connectivity related files (3G internet, APNS etc) right? So its better not to touch them when flashing custom ROM/kernel?
Thanks a lot again!
JJEgan means it's really hard to get to brick your SGS.
The kernel is responsible for the proper functionality and cooperation between hardware parts. As for SGS, it is a common belief that Samsung's RFS is not as robust or "agile" as ext4 FS. Thus, converting RFS to ext4 should increase device's performance (the time needed for the read/write operations to take place is decreased). BUT, in order for the device to function properly, the kernel MUST support ext4 as a file system format otherwise it won't work anymore (This could happen after installing a stock kernel on a device that uses some filesystem apart from rfs). Samsung's stock kernel does not, so you have to replace it, if that's the case.
(E.g. If you format a USB drive under Windows 7 with "exFAT" as its filesystem, you won't be able to access it through Windows XP for example, because XP does not support "exFAT" - Different kernels & Different OS version ).
Yes, CSC and modem.bin are what makes your device a TELEPHONE, too Connectivity issues between your operator and your handset depend on those files. If you can find the latest COMPATIBLE modem file, then go for it.
Thanks for the explanation!
As for CSC and modem, by compatible you mean the same version (XXJPY for example)? How do I know they are compatible with my phone?
Thanks a lot again!
the CSC doesnt have to match the baseband. for exapmle, you can have XXJPY baseband and XXJQ1 modem. (thats what i used to run)
its all about finding the right modem for your region, you want to make sure you get good connections dont ya ? modems affect SMS, Calls, Data, WIFI, so on.....
so you want the right one. If you go to rom kitchen, you can see all the modems and what region they cover
Thanks!
But is there a way not to touch the CSC/modem when flashing custom kernel/ROM? I'm really afraid to mess with those.
Also could someone refer to this question:
Also I'm having a hard understanding, if kernel is the thing that manages the hardware and also responsible for lagfix then kernel is really what matters for the performance of the phone. How a ROM could improve phones performance?
Click to expand...
Click to collapse
Thanks a lot again, and sorry for a bunch of questions!
So is the pda is the kernel then if you are flasing pda/modem/csc?
Yes, PDA is a kernel
skwo said:
Thanks!
But is there a way not to touch the CSC/modem when flashing custom kernel/ROM? I'm really afraid to mess with those.
Also could someone refer to this question:
Thanks a lot again, and sorry for a bunch of questions!
Click to expand...
Click to collapse
Think of the kernel as the drivers and the ROM as the OS. If your drivers are from 1987, windows 7 wont run well, if at all. However, you can have the newest 2011 drivers installed on Windows 95....same thing. Kernel and ROM must be well suited and work together for a good experience.
Sent from my GT-I9000 using xda premium
X-GoD said:
So is the pda is the kernel then if you are flasing pda/modem/csc?
Click to expand...
Click to collapse
Actually if you are flashing a three file firmware with odin, PDA is the ROM, which in this case usually includes a kernel.
If you are flashing a kernel alone onto an already installed ROM, then the kernel is put in the PDA field.
Sent from my GT-I9000 using xda premium
Gingerbread needs a different kernel than Froyo, right?
every firmwarerelease (JVQ, JVP, JVR, JVS, etc..) has its own kernel version.
but with talondev im not sure, cuz there is no distinction between the kernel versions.
with all other custom kernel releases you have specific kernel versions.
yep 10 charrrrr
Terranigmus said:
Gingerbread needs a different kernel than Froyo, right?
Click to expand...
Click to collapse
Yes, be sure to read the kernel's thread to check the version it is made for.
Sent from my GT-I9000 using xda premium
thehackman said:
every firmwarerelease (JVQ, JVP, JVR, JVS, etc..) has its own kernel version.
but with talondev im not sure, cuz there is no distinction between the kernel versions.
with all other custom kernel releases you have specific kernel versions.
Click to expand...
Click to collapse
Actually most custom kernels can work with any firmware build for the same version, froyo or gb. Some devs may base a kernel on a specific firmware, but they usually work on all.
Sent from my GT-I9000 using xda premium
I found the following link that briefs the options that you are looking for. I know this is an old post but thought posting here would help others as well.
donandroid.com/understanding-odin-a-beginners-guide-on-odin-buttons-checkboxes-629
Thanks,
Uresh
skwo said:
Hi there! I'm new to the forum and to android as well.
As you can guess I'm a proud owner of SGS
Since my SGS sucks a bit (random crashes, reboot, RFS) I'm interested in taking the maximum out of it, and I have some questions.
What is the difference between kernel and a rom? As far as I know from Linux and OS theory, kernel is the layer between the user (applications) and the hardware. I also know that most of the ROMs have kernel in them. Then what else the ROM contains?
What is firmware? Is it used a synonym for kernel/rom?
Is it worth installing custom kernel/rom on SGS? I'm a bit paranoid in those things and have some fears about the issue.
Is there a way to install some good kernel (like speedmod) and naked ROM (not someones mod, i.e. a stock android ROM without any additions from third party developers)? Is it hard to make my own ROM based on stock ROM (without touching the kernel, even tough I looked at the code and read books about the linux kernel, I dont yet consider my self a guru to be able to make my own kernel for android), just the modification and custom applications?
Thanks a lot guys!
Click to expand...
Click to collapse
uresh.kuruhuri said:
I found the following link that briefs the options that you are looking for. I know this is an old post but thought posting here would help others as well.
donandroid.com/understanding-odin-a-beginners-guide-on-odin-buttons-checkboxes-629
Thanks,
Uresh
Click to expand...
Click to collapse
thats quite old link u brought up here..........
Sent from my GT-I9000 using xda app-developers app
I bought my Captivate in December, and have since rooted, updated to Froyo through Kies, and even flashed a couple of kernels (currently running Firebird). I log onto and read posts on XDA almost daily, its kind of like my daily newspaper! Anyway, I have never understood how its possible that so many members have an i897 Captivate-based phone, yet is able to run i9000-based modems, kernels and ROMS. I've searched and googled, and can't get a straight answer, maybe my search terms need improvement, I don't know. But, is it possible to have
i9000 ROMS (with a i9000 modem/kernel of course) on our United States i897 Captivate? Or, is it that more members on this forum have i9000 based phones than I thought?
aicirt17 said:
I bought my Captivate in December, and have since rooted, updated to Froyo through Kies, and even flashed a couple of kernels (currently running Firebird). I log onto and read posts on XDA almost daily, its kind of like my daily newspaper! Anyway, I have never understood how its possible that so many members have an i897 Captivate-based phone, yet is able to run i9000-based modems, kernels and ROMS. I've searched and googled, and can't get a straight answer, maybe my search terms need improvement, I don't know. But, is it possible to have
i9000 ROMS (with a i9000 modem/kernel of course) on our United States i897 Captivate? Or, is it that more members on this forum have i9000 based phones than I thought?
Click to expand...
Click to collapse
Im just taking a shot here, but i think its because our roms are based off the i9000 roms... (theyre not the same, but theyre in the same class...)
aicirt17 said:
But, is it possible to have
i9000 ROMS (with a i9000 modem/kernel of course) on our United States i897 Captivate?
Click to expand...
Click to collapse
Yes. If you flash a stock version of an i9000 ROM then you will have orientation and Home button issues though. That is why there are kernels in the Captivate development section that are based on i9000 source code and reoriented along with other tweaks. You should also take care to read and understand exactly what it is that you are doing before attempting to flash any ROM, especially one made for an extremely similar, yet different, phone.
As I've learned the hard way, make sure to stay in the captivate development section. There are plenty of I9000, roms to pick from that will work fine for your i897. Just make sure to either use the kernel with the rom or pick a reoriented one. Keep in mind there is some call quality loss with the i9000 roms. And most of all, be careful with bootloaders.
Sent from my SAMSUNG-SGH-I897 using XDA App
cardassianvol said:
Yes. If you flash a stock version of an i9000 ROM then you will have orientation and Home button issues though. That is why there are kernels in the Captivate development section that are based on i9000 source code and reoriented along with other tweaks. You should also take care to read and understand exactly what it is that you are doing before attempting to flash any ROM, especially one made for an extremely similar, yet different, phone.
Click to expand...
Click to collapse
So, I can take my cappy as it is now (stock Froyo, Firebird kernel), and flash an i9000 ROM, making sure to also flash an i9000 modem and kernel (if the ROM doesn't already come with one), and that's it?
Cdub3 said:
As I've learned the hard way, make sure to stay in the captivate development section. There are plenty of I9000, roms to pick from that will work fine for your i897. Just make sure to either use the kernel with the rom or pick a reoriented one. Keep in mind there is some call quality loss with the i9000 roms. And most of all, be careful with bootloaders.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Bootloaders, the one thing I haven't read up on yet. Think I'll read, read, read, and then read a little more after that. I forgot about the bootloaders. Thanks for the heads up Cdub3!
aicirt17 said:
Bootloaders, the one thing I haven't read up on yet. Think I'll read, read, read, and then read a little more after that. I forgot about the bootloaders. Thanks for the heads up Cdub3!
Click to expand...
Click to collapse
u only need to get acquainted with bootloaders if you are planning to jump to a gingerbread ROM other than cyanogenmod7 or miui from 2.1/2.2 ROMs. GB bootloader+2.1/2.2 secondary bootloader=
aicirt17 said:
So, I can take my cappy as it is now (stock Froyo, Firebird kernel), and flash an i9000 ROM, making sure to also flash an i9000 modem and kernel (if the ROM doesn't already come with one), and that's it?
Click to expand...
Click to collapse
it must be a REORIENTED kernel in order for it to work. in all honesty, i have found that its better to select any rom from the captivate section rather than using a straight i9000 rom from the i9000 forums. go ahead and try a few out, but you will quickly see why i would suggest getting one of the mature i9000 roms from the captivate section instead. references to front facing camera, lack of haptic feedback on the home key, and other little things will begin to creep up on you. it gets annoying.
aicirt17 said:
So, I can take my cappy as it is now (stock Froyo, Firebird kernel), and flash an i9000 ROM, making sure to also flash an i9000 modem and kernel (if the ROM doesn't already come with one), and that's it?
Click to expand...
Click to collapse
You should flash the i9000 ROM and then flash a reoriented i9000 kernel from the Captivate development section and while the modem must be an i9000 modem when using an i9000 based ROM, you should research which modems support your carrier best. I'll assume you are on AT&T and say you need a modem that supports the 850MHz band if you want 3G support everywhere AT&T offers it when you travel inside the US. The standard i9000 modems support the 1900MHz band, which AT&T uses in my area. I'd suggest following the guides in the Captivate Development section though. Most ROMs there have done this work for you. They are almost all based on the official i9000 releases. There is nothing wrong with playing around after you understand the basics though. I run stock i9000 Gingerbread with the i9000 reoriented kernel by xcaliburinhand. Then I tailor it to my liking.
Hi everyone, i am just curious here since everyone said that phone with a locked bootloader is unable to flash a custom rom. But what does it means actually? aren't there are all the custom rom around for our motorola milestone?
From my understanding so far(please correct me if i am wrong, i am a very new to android), locked bootloader means that we can only used a sbf files that are signed officially by motorola only? how they actually made a latest version of gingerbread to milestone? there are tons of question mark in my head i hope someone will be kind enough to clarify to this newbie. Thanks alot.
No one who can provide an answer?
I'm currently thinking about, flashing Cyanogen 7 on my Milestone. However I would like to understand, how it works to run a Rom on a signed boot loader.
Resp. what the drawbacks are (longer boot time?).
Thanks in advance to anyone who can shed a bit of light on this topic.
234m said:
No one who can provide an answer?
I'm currently thinking about, flashing Cyanogen 7 on my Milestone. However I would like to understand, how it works to run a Rom on a signed boot loader.
Resp. what the drawbacks are (longer boot time?).
Thanks in advance to anyone who can shed a bit of light on this topic.
Click to expand...
Click to collapse
Basically what this is, is almost like a Froyo ROM that is running on the least amount of Froyo available (to bypass the signature verification of Motorola's locked bootloader). So even though the kernel shows that it's 2.3.7, it is based off of a Motorola kernel and exploited to port Gingerbread onto the Milestone.
If the bootloader was really unlocked, we would be able to change the kernel, which could improve optimizations for the phone, the CPU, etc. and it has true overclocking of the CPU.
Thanks skadude66, for your explanation
skadude66 said:
So even though the kernel shows that it's 2.3.7, it is based off of a Motorola kernel and exploited to port Gingerbread onto the Milestone.
Click to expand...
Click to collapse
So it is like turning a Dodge Neon into a Dodge Caliber just by changing it's chassis and leaving the engine?
Is the boot time of the exploited kernel longer than the vanilla version?
234m said:
Thanks skadude66, for your explanation
So it is like turning a Dodge Neon into a Dodge Caliber just by changing it's chassis and leaving the engine?
Is the boot time of the exploited kernel longer than the vanilla version?
Click to expand...
Click to collapse
What do you mean by vanilla version? Comparing 2.3.7 to the stock Motorola 2.2.1 kernel in terms of boot times?
skadude66 said:
What do you mean by vanilla version? Comparing 2.3.7 to the stock Motorola 2.2.1 kernel in terms of boot times?
Click to expand...
Click to collapse
Yes, that's what I mean. I imagine this system somehow like an "Virtual Machine", where you have to boot the "host" (2.2.1) before you can boot the "guest" (2.3.7).
Is it like this?
Is UCKH3 going to see a EXT4 lagfix, or is there another way I can do a EXT4 lagfix on my phone? I like to play games on my phone, and the games are very laggy. I love I9000 rom because they run very smooth, but can't get a modem that sounds as loud or as clear as the one in the captivate UCKH3. Can anyone please help. I've been searching xda developers every day in hopes that I will find a way to lagfix KH3. Thanks in advance.
No kernel source = no lagfix
Cog 5 got ext 4 and it had no source.... I admit odds of getting ext 4 is slim with out the source.
studacris said:
No kernel source = no lagfix
Click to expand...
Click to collapse
KF1 had ext4 support built in to the kernel apparently. No source needed. As far as if the KH3 kernel also supports ext4, what else is needed, or what method designgears used to convert the partitions you could send him a private message and see if he can provide the details. You could even just check out the cog 5 v2 package yourself.
No DesignGear's method was unfinished. Converting to ext broke alot of things. It is possible though, but when coding the kernel with out the source you usually end up braking things in the process.
prbassplayer said:
No DesignGear's method was unfinished. Converting to ext broke alot of things. It is possible though, but when coding the kernel with out the source you usually end up braking things in the process.
Click to expand...
Click to collapse
What was unfinished? The kernel supported ext4 out of the box, he bundled in the required e2fsprogs and he scripted the partition conversion before the firmware gets installed.
There is no way to revert without using heimdall (or odin) since you need to re partition, but functionally, he did the job.
v2 seemed to run fine for me for what it was. What was broken exactly? It didn't seem like a lot was broken.
Alot of small things. Wifi would connect but wouldn't reconnect automatically. I don't remember exactly why I moved away from it. Thing is on my phone worked well enough to be a daily driver but not for alot of people. Thing is it is possible to enable ext4, but with out source you end up braking stuff.
prbassplayer said:
Alot of small things. Wifi would connect but wouldn't reconnect automatically. I don't remember exactly why I moved away from it. Thing is on my phone worked well enough to be a daily driver but not for alot of people. Thing is it is possible to enable ext4, but with out source you end up braking stuff.
Click to expand...
Click to collapse
Fair enough. I just wonder how much of it was 2.3.3 to begin with.
So you Guy's mean I can't get ext4 without a kernel? If the uckh3 kernel supports ext4 then there has to be a program out there. I also had cog v2 installed but I never had ext4 on that rom either. I also had voodoo control and never saw an option for lagfix on cog v2.
Sent from my SAMSUNG-SGH-I897 using XDA App
If you had V2 then you where running in Ext4 format. There was no Voodo lag fix per say, but the filesystem was in ext4 format (exactly what Voodoo lag fix does.)
lildoggs said:
Is UCKH3 going to see a EXT4 lagfix, or is there another way I can do a EXT4 lagfix on my phone? I like to play games on my phone, and the games are very laggy. I love I9000 rom because they run very smooth, but can't get a modem that sounds as loud or as clear as the one in the captivate UCKH3. Can anyone please help. I've been searching xda developers every day in hopes that I will find a way to lagfix KH3. Thanks in advance.
Click to expand...
Click to collapse
Just a thought, but couldn't you just flash the kh3 modem to a I9000 rom and therefore have the smoothness that galaxy s roms give but with the loudness of the captivate speaker? I was on apex 8.2 with kh3 modem and everything worked great. Though whenever wifi was on people complained of an Echo effect.
No. you do not mix I897 modems with I9000 kernels or vice versa. It causes problems, like you mentioned the echo, other problems vary including loss of audio completely on calls...
studacris said:
No. you do not mix I897 modems with I9000 kernels or vice versa. It causes problems, like you mentioned the echo, other problems vary including loss of audio completely on calls...
Click to expand...
Click to collapse
I have had the audio loss as well... a simple switch to speakerphone and back fixed it. Was unaware that was a modem/rom compatibility problem.
Luckily, I only use my Captivate as an Media Player or for WIFI surfing. The KH3 modem over Apex worked great for me. WIFI has been stable, battry life is better than the non-lagfixed I897 Roms of any flavor and speed is noticeably faster as well.
jbabbler said:
Luckily, I only use my Captivate as an Media Player or for WIFI surfing. The KH3 modem over Apex worked great for me. WIFI has been stable, battry life is better than the non-lagfixed I897 Roms of any flavor and speed is noticeably faster as well.
Click to expand...
Click to collapse
So, you have a phone that you never make calls with?
Yep it was purchased as a replacement to my iPod touch. I will never go back to iPod.
Sent from my SAMSUNG-SGH-I897 using XDA App