Since i couldn't find any similar thread, here is my problem:
I used every Cognition ROM, since SRE 1.3.1c to Beta7, but always noticed that the SMS order was wrong.
I'd a 5-6 minutes difference between sent and received sms. So, my sent messages were located in the bottom, and the received in the top, making them difficult to read..
Now, i'm using Shep's ROM with xcaliburinhand Kernel, and i noticed that my SMS are place in order now! No timming issue!
But.. With Cognition Beta7 my battery lasted 25-40 hours!!
And, with Shep's ROM, only last 10!
Any suggestions?
Thanks!
i can't even send a sms/mms at all at cog 2.2 beta7....
Juat waiting beta8
Sent from my SAMSUNG-SGH-I897 using XDA App
I am not sure What is going on with both of your issues, I have been using Cog on and off sense SRE started and have never had those issues, SMS ordering was never an issue and have not had trouble sending out mms. Are you guys useing TBU to restore settings?
Same here. I am on cog6 with no sms or mms issues.
My procedure is always the same:
- Stock with odin JF6
- Root
- Flash any ROM with Clockwork Recovery Mode
I never used any Backup (Except Google's contacts, GMail and Calendar). I never trusted any settings backup..
I'll try Cog B7 with xcaliburinhand's kernel, and others combinations..
But i really want to know if it's a Modem, Kernel or ROM issue, 'cause if it's a Modem fw issue, i could flash anything, and then, flash the Working (no issue) modem over.. Just to be prepared..
Thanks!
I think it's an issue with the Carrier timestamps. If you install Handcent and look at your messages, you'll see they will be put in order. I had the same thing happen to me a day or so after I installed 2.2, but never had it happen on 2.1
miztaken1312 said:
I think it's an issue with the Carrier timestamps. If you install Handcent and look at your messages, you'll see they will be put in order. I had the same thing happen to me a day or so after I installed 2.2, but never had it happen on 2.1
Click to expand...
Click to collapse
I to use handcent and have not experienced this issue
Sent telepathically using vulcan mind meld app.
SnakeHaveYou said:
My procedure is always the same:
- Stock with odin JF6
- Root
- Flash any ROM with Clockwork Recovery Mode
I never used any Backup (Except Google's contacts, GMail and Calendar). I never trusted any settings backup..
I'll try Cog B7 with xcaliburinhand's kernel, and others combinations..
But i really want to know if it's a Modem, Kernel or ROM issue, 'cause if it's a Modem fw issue, i could flash anything, and then, flash the Working (no issue) modem over.. Just to be prepared..
Thanks!
Click to expand...
Click to collapse
I noticed that there is one diff in how we flash a new rom
Odin one click
Master clear with odin one click
Root
Rom manager flash
you might want to back up with Titanium back up you user apps as the master clear will wipe the device. might be something left over from a stock flash that may mess you up. but that is just my 2 cents
miztaken1312 said:
I think it's an issue with the Carrier timestamps. If you install Handcent and look at your messages, you'll see they will be put in order. I had the same thing happen to me a day or so after I installed 2.2, but never had it happen on 2.1
Click to expand...
Click to collapse
Yep, it's a Carrier issue (and it get worst sending SMS between different carriers!) But, i had this issue in Stock Eclair, SRE Eclair, Cog Eclair and Cog Froyo.. It only gets fixed with Shep's ROM, that's the weird thing
zelendel said:
I noticed that there is one diff in how we flash a new rom
Odin one click
Master clear with odin one click
Root
Rom manager flash
you might want to back up with Titanium back up you user apps as the master clear will wipe the device. might be something left over from a stock flash that may mess you up. but that is just my 2 cents
Click to expand...
Click to collapse
Yes, i do the Master Clear too.. Also Dalvik, Cache, Battery and Data wipe from Clockwork..
Well.. Testing, after Back to Stock JF6, Master Clear, Data, Battery, Dalvik and Cache Wipe:
- Cognition 2.2 Beta7 > SMS timming issue
- Cognition 2.2 Beta7 + xcaliburinhand's Reoriented 2.0.1 Kernel > SMS timming issue
- Cognition 2.2 Beta7 + xcaliburinhand's Reoriented 2.0.1 Kernel + JH2 Modem > SMS timming issue
- Shep's Stock ROM + xcaliburinhand's Reoriented 2.0.1 Kernel > SMS timmng fixed
So, the only thing that fix this problem is the Shep's Stock ROM..
SnakeHaveYou said:
Yep, it's a Carrier issue (and it get worst sending SMS between different carriers!) But, i had this issue in Stock Eclair, SRE Eclair, Cog Eclair and Cog Froyo.. It only gets fixed with Shep's ROM, that's the weird thing
Click to expand...
Click to collapse
That's the reason I noticed it. I was texting my ex girlfriend who uses Sprint, my cousin on Verizon, one of my girl friends on T-Mobile, and my best friend on AT&T. Everyone was messed up except my best friend. Or maybe its cause the other three are female. Who knows. I'd place a wager on the Carriers just to be safe and not get yelled at. :-D
Sent from my Captivate
Hmm..
I had the MMS/SMS timing bug with Cog's 2.1.6 build.
I'm on Cog's 2.2.6 Froyo and haven't experienced any issues.
And my txts are all over the place... my brother who is on Sprint, a buddy in town on T-Mobile, and my sister-in-law who is on Verizon on a Kansas phone # (and I'm in Colorado).
I dunno.. seems to be pretty random.
Last load was Odin back to stock.
Then used ROM Manager to update to Cog's 2.2 build.
Related
When I was on DocRambone's 7.5 JPA with the older ReOrient kernel 2.1.1 I never had soft reboot problems and then it seems I started getting them after a lot of the Captivate kernels started incorporating these small tweaks.
After reading a lot of other posts other people have been having this same problem but we have no idea what is causing it. At first I thought it was one of the tweaks that you enable in the new recovery ULF tweak section but after disabling all those tweaks and doing a factory reset I was still getting them.
I tried a very untweaked setting with haptic feedback and only bln (no lagfixes, etc...) and it still happened.
Has anyone been able to find the culprit? I've tried 2 different kernels: Reorient and SetiroN's.
When I have my phone in my pocket and I'm driving I'll randomly feel haptic feedback even though I dont have a call or text and shortly thereafter I'll get 2 small vibrations and then a reboot. Once it reboots it seems to come back up for a few minutes and reboot again. I was using ChompSMS with BLN and haptic enabled and that was pretty much the only things I changed from stock.
P.S - The purpose of this thread is to put a collaborative effort in finding out WHY our phones are restarting for some unknown reason. As this community and devs grow, sometimes problems like this arise.
I have seen a few post about the reboots. I have never had any with the kernels. Its kinda strange some of us dont have the issue.
there are several reasons for soft reboots.
if you are running an i9000 rom with a captivate modem, you will get them
if you are running an i9000 rom with a particular modem that doesnt work in your area, you will get them when the modem tries to hand off between towers.
you can get them from oc/uv, bad framework hacks, bad rom, etc. it is all circumstantial, it all depends on what changes you have made from stock....
Pirateghost said:
there are several reasons for soft reboots.
if you are running an i9000 rom with a captivate modem, you will get them
if you are running an i9000 rom with a particular modem that doesnt work in your area, you will get them when the modem tries to hand off between towers.
you can get them from oc/uv, bad framework hacks, bad rom, etc. it is all circumstantial, it all depends on what changes you have made from stock....
Click to expand...
Click to collapse
The DocRambone 7.1 and 7.5 I9000 ROM uses the JPP modem if I'm not mistaken, and I never had reboots. It wasn't until I went to reorient kernel 2.1.2 (or 2.1.3 can't remember) that these reboots occurred.
Right now I'm doing Doc 7.6 MikeyMike01 with JG8 modem and SetiroN 1.2. I also had a previous setup of using JPP and a different rom with both kernels and had reboot problems.
If the modem is somehow causing reboots I may go to the stock captivate modem and see what's going on.
So far in my apartment the phone has not rebooted by itself (has had a constant HSUPA connection). I'm also running the ROM stock without recovering any of my apps. When I leave here soon I'll see if my phone restarts. If it does, then it would appear a modem issue may be at hand.
smokestack76 said:
I have seen a few post about the reboots. I have never had any with the kernels. Its kinda strange some of us dont have the issue.
Click to expand...
Click to collapse
What type of setup do you have?
LinuxNewb said:
What type of setup do you have?
Click to expand...
Click to collapse
Cog 2.3b modded with setiroNs kernel. No oc/uv enabled, Using the jpp modem with Hsdpa working.
For some reason clearing dalvik cache and fix permissions in recovery did it for me..i haven't reboot since
xdaApp via Captivate
darkamikaze said:
For some reason clearing dalvik cache and fix permissions in recovery did it for me..i haven't reboot since
xdaApp via Captivate
Click to expand...
Click to collapse
If my phone crashes ill try that and see if works. So far at home it's been perfect.
LinuxNewb said:
If my phone crashes ill try that and see if works. So far at home it's been perfect.
Click to expand...
Click to collapse
That makes me think modem.
smokestack76 said:
That makes me think modem.
Click to expand...
Click to collapse
why is that .. ? soft reboots did only happen to me when I wasn't home lol
darkamikaze said:
why is that .. ? soft reboots did only happen to me when I wasn't home lol
Click to expand...
Click to collapse
as i stated earlier, the soft reboots usually occur due to modem/rom incompatibilities when the modem is trying to hand off from network to network.
this was a part of our experiments with the ji6/jpk roms that boomerod, shep, and several others were testing. it has to do mostly with the 850mhz frequency.
interesting.. well i'm on JPP right now.. so far stable
darkamikaze said:
interesting.. well i'm on JPP right now.. so far stable
Click to expand...
Click to collapse
i am on jpp right now also, and am about to go for a drive to make sure its completely stable with the handoffs.
I remember one time i did a certain combination of install rom, restore apps and apply jfs lagfix and a popup came up that said i had mismatching uid's and that i had to format /data directory.
Sure enough soft reboots all.over the place after some fc's.
I found that the best way to use the lagfix is to restore apps b4 lagfix and activate the tweaks at the same time as the fix. It works for me
Sent from my GT-I9000 using XDA App
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
fatttire said:
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
Click to expand...
Click to collapse
Ya... as soon I started driving my phone would restart. When it's at home nice and solid connection theres no problem lol
So if we narrowed it down to a possible modem issue lets start testing which ones work.
Fatttire - If you could attach the modem you're using so we can try it out that'd be cool did anyone play with the combi bands or any other settings within the service mode?
tytdfn said:
I remember one time i did a certain combination of install rom, restore apps and apply jfs lagfix and a popup came up that said i had mismatching uid's and that i had to format /data directory.
Sure enough soft reboots all.over the place after some fc's.
I found that the best way to use the lagfix is to restore apps b4 lagfix and activate the tweaks at the same time as the fix. It works for me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I didn't even restore apps or do any lagfixes and I'm having this issue Good to see yours worked for you though. Hopefully we'll find a modem thats compatible with this JPA/JPP setup.
I've only used stock modems on our two captivates - occasionally they will restart out of the blue.
Once in particular I think it was because of a live wallpaper. After disabling it, everything seemed smooth running again. I just use plain black wallpaper and mine never reboots.
K-mart Shopper said:
I've only used stock modems on our two captivates - occasionally they will restart out of the blue.
Once in particular I think it was because of a live wallpaper. After disabling it, everything seemed smooth running again. I just use plain black wallpaper and mine never reboots.
Click to expand...
Click to collapse
Ive done so many weird configs of roms/firmware/kernel/custom frameworks and I've never had an issue with reboots. I ran a 2.1 i9000 setup with HSUPA and that never ever reset on me.
JG8 is only to start with to enable 850
fatttire said:
The JG8 modem for me in Shep's ROM causes frequent soft reboots. As soon as I get rid of it, problem solved.
Click to expand...
Click to collapse
The JG8 is an Eclair modem, not Froyo. Its purpose is to use at the beginning of an install from stock JF6. Once you have the rom and kernel you want, you need to replace it with a Froyo (suggest JPP) modem.
Don't leave yourself running a Froyo (i.e. Shep) rom with an Eclair modem, you are just asking for trouble.
I tried a couple of 2.2.1 roms but found I lose signal using them and the browser doesn't work quite right. when I try going back to 2.2 the apps don't restore correctly. Some restore. Most don't have their data restored correctly and some don't restore at all. TiB doesn't throw any errors. I've tried many roms and I can restore to any 2.2.1 rom but I have the same problem with any earlier rom. Is there any fix?
k2snowboards88 said:
I tried a couple of 2.2.1 roms but found I lose signal using them and the browser doesn't work quite right. when I try going back to 2.2 the apps don't restore correctly. Some restore. Most don't have their data restored correctly and some don't restore at all. TiB doesn't throw any errors. I've tried many roms and I can restore to any 2.2.1 rom but I have the same problem with any earlier rom. Is there any fix?
Click to expand...
Click to collapse
I noticed this as well. I think it is due to the differences in the way the 2 handle program settings. No fix that I am aware
I hope there's a good captivate based 2.2.1 in the future. I'm not willing to give up my app data, but I'm also sick of losing signal ever time I charge my phone. Hopefully there's a new 2.2.1 cap leak soon. Or a TiB update to handle this.
k2snowboards88 said:
I hope there's a good captivate based 2.2.1 in the future. I'm not willing to give up my app data, but I'm also sick of losing signal ever time I charge my phone. Hopefully there's a new 2.2.1 cap leak soon. Or a TiB update to handle this.
Click to expand...
Click to collapse
Might be awhile as all the 2.2.1 leaks are i9000 leaks and the Cap is still waiting for the source from 2.2 which we still dont have. I have never had an issue of losing signal when charging.
zelendel said:
Might be awhile as all the 2.2.1 leaks are i9000 leaks and the Cap is still waiting for the source from 2.2 which we still dont have. I have never had an issue of losing signal when charging.
Click to expand...
Click to collapse
I've read that there are different physical modems used in some captivates. Some of them can't handle the i9000 modem software. There are a few very long threads on the issue. Unfortunately, all of the devs got the lucky modems, so none of them care about the issue.
A bit late, but I had virtually no problems batch-restoring a TiBu from (over 150 apps) a 2.2.1 ROM to a 2.2 ROM with the experimental 'Migrate' option checked in the preferences. I was even able to restore contacts and dialer history.
GGXtreme said:
A bit late, but I had virtually no problems batch-restoring a TiBu from (over 150 apps) a 2.2.1 ROM to a 2.2 ROM with the experimental 'Migrate' option checked in the preferences. I was even able to restore contacts and dialer history.
Click to expand...
Click to collapse
I don't know what's going on for me then, because I've tried that too. It doesn't work for me.
k2snowboards88 said:
I don't know what's going on for me then, because I've tried that too. It doesn't work for me.
Click to expand...
Click to collapse
Contacts and dialer history, and alarms can be restored. These are the only two "system" apps I keep backing up and restoring on various 2.2 and 2.2.1 ROMs. But on some ROMs, apps get restored, but not data. And sometimes some apps data is restored, while of others apps isn't.
k2snowboards88 said:
I don't know what's going on for me then, because I've tried that too. It doesn't work for me.
Click to expand...
Click to collapse
Hmm, well a bit of an update. It seems to vary from ROM to ROM. I restored a backup from a JPY 2.2.1 ROM (Darky's 8.1) to a Rogers 2.2 ROM (Firefly 1.5) and everything restored perfectly. I later restored the exact same backup to an Armani 2.2 ROM (Andromeda) and while all apps restored successfully, some apps were missing their data. On top of that, restoring LauncherPro backups seems to be sporadic with most ROM's only restoring the homescreens and first dock, others restoring all docks and even internal settings.
I'd like to flash to Cog 3.04 directly if possible without Odin'ing back to 2.1. Is it ok to flash directly to 3.04 and if so, what the best way to wipe everything first to start form as blank a state as possible? I'm without a windows PC right now...
Thanks!
hate to bump but if anyone can provide a quick answer... thx.
I flashed 3.04 over 2b8 without any problem.....
You can try that but no guarantee that it will work.you may run into problems and have to flash back to odin then you will be sol with out a computer
Sent from my SGH-I897 using XDA App
You should be fine flashing from one version to another. If you enabled lagfix I'd disable that first, and to be on the safe side do a CWM backup, but other than that you should be fine. I've been flashing another ROM back and forth without going stock many times without issue.
You can go and flash custom ROMs on top of each other and it might work, but don't be surprised if you boot into Cog 3.04 and have to deal with a bunch of force closes or other weird behavior.
I ALWAYS recommend people flash back to stock and Master Clear/GSM Master Reset. That gives you a blank slate to work with. It takes less than 10 minutes, but some just believe that's too much work/time for them.
Your call.
I've never had an issue flashing updates on top of Cognition. I'm pretty sure as long as your lag fix is the same between versions then there should not be any problems.
I flashed serendipity 5.0 over 4.3 last night with no problems. I just disabled lagfix before I did.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks everyone for your helpful input.
Is it possible to master clear without going back to stock? I'd like for everything except the external sdcard to be cleared.
Hey I have a question I am on Darkyy 9.3 and have flashed to stock before numerous times and have a Download Mode Jig always handy but I have been hearing and reading recently that with good ROMs with the new install script that you can just flash ROMs over each other if you wipe data and cache and dalvik cache and if you get in trouble just flash to stock.
The reason this interests me is because im a build 1011 and its super annoying because I have to flash to JH3, then Root, then apply 3 button fix.zip sometimes if the 3 buttons dont work, ROM Manager, Quick Boot, JH7ota.zip, then flash the next ROM.
I am willing to do this but I am feeling lazy today and wanna try out Serendipity so Im asing YOU do you think i'll be alright if I flash Serendipity JS3 over a JS5 Darkyy 9.3?
Also one more questions related to that is Serendipity users does it overwrite your Kernel and modem when flashing? I have Suckerpunch and JL3 and am wondering if I should disable lag fix-->Install latest Speedmod. Or would the ROM script just overwrite that.
Finally a question that was posed to me today from a user that doesnt flash to stock and hasnt had a problem that really made me think that what really is the difference when using Odin which installs an unneccesary bootloader and ect going from a JS5 base to a JH3, then using CWM to go JS5 to JS3? Wouldnt it seem logically easier and safer?
Any input and comments about your experience will be GREATLY appreciated.
you can use odin1click, or odin3...
since you have a jig, flashing to stock is not a big deal to you.
Owais1437 said:
you can use odin1click, or odin3...
Click to expand...
Click to collapse
he cannot use odin 1click since the build is 1011. it will brick the phone, for sure.
I Odin3 back to stock, but I'm also on the safe side. I have heard more and more people flash over the old ROM with using Odin though.... I figure that it only adds a few more minutes to the overall task, so why not?
always flash stock imo
just best to go to stock , flashing over has created small bugs for me ..., i do this even for common builds or updates, even though the Dev's work hard to make them upgradeable...i still do .....and if your courageous,,, its good you have the jig or a 1007 build
My personal choice is flash to stock if the roms use different kernels. If the kernel is the same, even different revs of same, I don't bother with stock.
Sent from my Captivate using XDA App
mengbo said:
he cannot use odin 1click since the build is 1011. it will brick the phone, for sure.
Click to expand...
Click to collapse
I use print one click all the time and my phone is build 1012
Sent from my SAMSUNG-SGH-I897
I always flash to stock and go through the whole process. I find it less buggy and the mental idea of a clean slate allows me to address issues solely on that rom and not past components.
It's sure as heck faster to flash to stock than to read through 1000's of posts to figure out if it's a good idea or not when I don't know as much about it...
I'm still new to the flashing ROMs world, but I'd rather be safe than sorry at this point so I go back to stock whenever I switch.
Ive now just wiped data cache and dalvik cache, and flashed over 4 ROMs in the past week with ZERO problems.
That being said im always safe I do it at home with my jig and odin ready on my PC.
But i actually havent had a single problem.
Darkyy-->Andromeda-->Paragon-->Serendipity
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...