Related
Ok so for the last few months, I have been switching between roms, looking for something with good battery life.
Every rom i tried, the battery life often was awful (10-12 hours light use) until pinnacle came around. With pinnacle, the standby drain was around 1% per hour, and it just kicked ass.
After pinnacle i went and tried cyanogenmod again, and to my dismay, the battery life still sucked. So back to pinnacle i went.
Then someone said to me that i dont have to go through all the hassle of flashing back to jf6 and having old bootloaders and all that crap was unnecessary, so i decided to see if i got better results in CM coming from pinnacle.
Well IT WORKED!!!!!!!!!!!! Battery life is on par with pinnacle as far as i can tell.
My previous method was:
flash back to jf6 via one click odin
root phone and install rom manager
install cwm for captivate
then choose mtd 2xx
then boot into recovery
wipe data, cache, and dalvik cache
install cm7 zip and gapps zip
My new method:
follow pinnacles instructions to install pinnacle
boot into recovery
wipe data, cache, dalvik cache, battery stats
install cm7 and gapps
So my possible conclusions are:
-That one click jf6 package sucks, theres no reason to every flash back to it. I plan on finding a different one click if i ever need to flash back to stock. Ill probably use a 2.2 or 2.3 one click
-CM is not completely wiping everything when it installs, and somehow performs better when coming from a gingerbread rom, than coming from eclair.
-I have wiped the battery stats in the past, but maybe doing it right away helps?
-cm7 build 181 is wayyy better than 179 - (not likely)
Not sure what else it could be. The same apps are always installed. I tried both the stock kernel and glitch v12 last time and both had bad results. This time im using stock with great results, and i havent had the urge to switch, because i dont wanna mess it up.
Hopefully this helped someone, or at least shed some more light on way some people get terrible battery life with some roms. I bet using this same method, I would get better results with roms I've tried in the past (APEX, MIUI, any other i9000 based roms)
They should really change the directions to CM if this is the case. Maybe this isnt the best for everyone, but the gingerbread bootloaders that come with pinnacle seem to work fine with CM, so why make people waste their time.
Under what usage conditions are you getting 1%/hr?
With data and wifi off I get about 1%/hr
all on 10%/hr
The big battery killer for me seems to be when the phone is searching for data signal. I had my phone at a customer site with no AT&T 3G coverage and no wifi to tap into. My drain was about 22% an hour. I almost crapped my pants when I checked the time about two hours into my day and I was at 55% (first time I looked at the phone in two hours).
When I get to work, if I forget to connect to wifi, I get around 10% per hour drain because the 3G signal in my building isn't that great. That's with minimal use.
If I get to work and connect to wifi, my battery drain is about 5% an hour with minimal use.
lourivellini said:
Ok so for the last few months, I have been switching between roms, looking for something with good battery life.
Every rom i tried, the battery life often was awful (10-12 hours light use) until pinnacle came around. With pinnacle, the standby drain was around 1% per hour, and it just kicked ass.
After pinnacle i went and tried cyanogenmod again, and to my dismay, the battery life still sucked. So back to pinnacle i went.
Then someone said to me that i dont have to go through all the hassle of flashing back to jf6 and having old bootloaders and all that crap was unnecessary, so i decided to see if i got better results in CM coming from pinnacle.
Well IT WORKED!!!!!!!!!!!! Battery life is on par with pinnacle as far as i can tell.
My previous method was:
flash back to jf6 via one click odin
root phone and install rom manager
install cwm for captivate
then choose mtd 2xx
then boot into recovery
wipe data, cache, and dalvik cache
install cm7 zip and gapps zip
My new method:
follow pinnacles instructions to install pinnacle
boot into recovery
wipe data, cache, dalvik cache, battery stats
install cm7 and gapps
So my possible conclusions are:
-That one click jf6 package sucks, theres no reason to every flash back to it. I plan on finding a different one click if i ever need to flash back to stock. Ill probably use a 2.2 or 2.3 one click
-CM is not completely wiping everything when it installs, and somehow performs better when coming from a gingerbread rom, than coming from eclair.
-I have wiped the battery stats in the past, but maybe doing it right away helps?
-cm7 build 181 is wayyy better than 179 - (not likely)
Not sure what else it could be. The same apps are always installed. I tried both the stock kernel and glitch v12 last time and both had bad results. This time im using stock with great results, and i havent had the urge to switch, because i dont wanna mess it up.
Hopefully this helped someone, or at least shed some more light on way some people get terrible battery life with some roms. I bet using this same method, I would get better results with roms I've tried in the past (APEX, MIUI, any other i9000 based roms)
They should really change the directions to CM if this is the case. Maybe this isnt the best for everyone, but the gingerbread bootloaders that come with pinnacle seem to work fine with CM, so why make people waste their time.
Click to expand...
Click to collapse
That´s great news!
Wich Pinnacle version were you in before flashing CM7?
minduka said:
Under what usage conditions are you getting 1%/hr?
With data and wifi off I get about 1%/hr
all on 10%/hr
Click to expand...
Click to collapse
everything on connected to wifi. I will post screenshots when i get home. I dont install too many apps, but i use facebook, twitter, beautiful widgets, and doggcatcher - which are apps that may possibly run in the background.
10 percent seems like a lot.
KreepyKen said:
The big battery killer for me seems to be when the phone is searching for data signal. I had my phone at a customer site with no AT&T 3G coverage and no wifi to tap into. My drain was about 22% an hour. I almost crapped my pants when I checked the time about two hours into my day and I was at 55% (first time I looked at the phone in two hours).
When I get to work, if I forget to connect to wifi, I get around 10% per hour drain because the 3G signal in my building isn't that great. That's with minimal use.
If I get to work and connect to wifi, my battery drain is about 5% an hour with minimal use.
Click to expand...
Click to collapse
yea i would definitely try reflashing. Try my method, and let me know if you get better results with that. Mine has been worse in the past, but never that bad.
alecao said:
That´s great news!
Wich Pinnacle version were you in before flashing CM7?
Click to expand...
Click to collapse
I was running pinnacle 1.2. I never felt the need to update to 1.3, and didnt want to risk it with the results i was getting.
Anyone who thinks the captivate sucks on battery should definitely try out pinnacle. And from there try out cyanogen again.
Hmm... I'll have to try that. I've been getting pretty terrible battery life with just about everything recently. Thanks for the tip.
Mr. Dr. Prof. Sean said:
Hmm... I'll have to try that. I've been getting pretty terrible battery life with just about everything recently. Thanks for the tip.
Click to expand...
Click to collapse
yea please try it and do exactly the same thing as i did. I would like to see if people get the same results as i did.
What ROM you're on before a flash does not matter. The script completely wipes the OS before the flash. So either way it's writing to an empty partition...
The only difference between both methods is the bootloaders, which may or may not be the reason for the results you're seeing.
studacris said:
What ROM you're on before a flash does not matter. The script completely wipes the OS before the flash. So either way it's writing to an empty partition...
Click to expand...
Click to collapse
thats exactly what i thought, so why should it even matter if i was on stock jf6 or not? (like it says in the instructions)
Somehow it is affecting it though, and i definitely have experienced better results. If i get a chance i will try flashing back to jf6 and doing it that way, and then doing it my way again. But im just listing what i did, and what my results were.
Thats why i was asking if it made sense.
Isolate the variables and test them individually. Like I said, the only difference is the bootloaders...so when you flash cm7 from jf6 again after you find out what the drain is like, flash JUST the gingerbread bootloaders while still running cm7 and see if it changes...
Jf6 one click doesnt suck, its just pointless and potentially harmful now.
I have been using uckf1 /w pit file to flash back to "stock" (if i need to repartition) but i removed the bootloaders from the package to avoid cataclysmic destruction.
Generally you don't need to flash back to stock at all anymore because most ROM's are full wipe.
studacris said:
Isolate the variables and test them individually. Like I said, the only difference is the bootloaders...so when you flash cm7 from jf6 again after you find out what the drain is like, flash JUST the gingerbread bootloaders while still running cm7 and see if it changes...
Click to expand...
Click to collapse
will try it out probably this weekend.
Question though: Should i just flash the gingerbread bootloader included in the pinnacle install, and then never touch the bootloader again? Ive heard the 2.3 bootloaders work universally, and that its a bad idea to flash bootloaders.
I used to always use the odin one click to jf6 whenever i would change roms. From now on i may use the 2.2 hemidall package i found. The only problem i see with that is it doesnt delete the data partition, and i think the last time i used it, it didnt delete apps i had installed, and i had force closes that made my phone unusable.
Why is flashing a rom on a phone more difficult than installing a OS on a computer.
Basically, i just want to completely format and do a fresh install everytime i put a new rom on. I dont see why things like data and cache arent wiped by default.
I personally like the odin one-clicks that end up erasing EVERYTHING and changes it exactly how it should be. Why are more roms available as odin one-click?
You only need Odin or heimdall as a recovery option from a soft brick, or to go back to a touch wiz based ROM from an aosp ROM (cm7/miui) as you need to repartition.
Just flash the Ginger boots and leave them alone, corrupted bootloaders from a bad flash is the only way to hard brick, so to minimize that risk flash bootloaders as minimally as possible (I only suggested that earlier as a suggestion for to to figure out if that was what helped), unless you have done the unbrickable mod then by all means flash your boot loading butt off with no worries.
So if you are on a touch wiz ROM, I897 or I9000 all you should have to do to is just flash over it. And if that goes sour and you can't boot back into cwm then, and only then, should you resort to Odin.
Think about it, if a ROM can flash over a stock ROM what is different about flashing over a custom ROM? Nothing.
If you want to make extra extra sure it's a "clean flash" you can wipe data/factory reset, wipe cache and dalvik cache and then flash, but the ROM should do that.
studacris said:
You only need Odin or heimdall as a recovery option from a soft brick, or to go back to a touch wiz based ROM from an aosp ROM (cm7/miui) as you need to repartition.
Just flash the Ginger boots and leave them alone, corrupted bootloaders from a bad flash is the only way to hard brick, so to minimize that risk flash bootloaders as minimally as possible (I only suggested that earlier as a suggestion for to to figure out if that was what helped), unless you have done the unbrickable mod then by all means flash your boot loading butt off with no worries.
So if you are on a touch wiz ROM, I897 or I9000 all you should have to do to is just flash over it. And if that goes sour and you can't boot back into cwm then, and only then, should you resort to Odin.
Think about it, if a ROM can flash over a stock ROM what is different about flashing over a custom ROM? Nothing.
If you want to make extra extra sure it's a "clean flash" you can wipe data/factory reset, wipe cache and dalvik cache and then flash, but the ROM should do that.
Click to expand...
Click to collapse
So if i decide to go back to pinnacle - i shouldnt one click jf6? But i at least need to hemidall - which doesnt flash bootloaders. And going from cm, i really dont even have to go back to jf6, i should probably at least go to one of the newer stock froyo roms.
Or even better - i should flash to a rom through odin that is already rooted and has cwm installed, so when i flash to a new rom, i dont have to manually root, and then install rom manager/cwm everytime. Right?
There are Odin packages without bootloaders...and heimdall ones with them.
Yes from cm7 you need to use Odin/heimdall. If using a non 1 click Odin you must place a .pit in the pit slot and a .tar in the pda. Which ever you use is up to you.
Serenity 6.1 seems to have a long life, contrasting with OR5 or Continuum6.2.1
Are you using the same modem that comes with CM7 (JL3) or did you flashed another one?
alecao said:
Are you using the same modem that comes with CM7 (JL3) or did you flashed another one?
Click to expand...
Click to collapse
Everything stock.
Sent from my SGH-I777 using Tapatalk
Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!
No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App
You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup
I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?
All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
2. Is there a performance difference between JB and ICS on the Cappy?
3. Should I go with a built-in kernel or flash a separate one?
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
5. I read on another post on the front page that the JB/ICS ROMs also use the internal SD card, mine is mostly full at the moment, how much space do the new ROMs take up?
Thanks for any help. Been considering flashing for a year but my phone recently got the lock screen button stuck problem and now I'm at a crossroads, either I buy a new phone entirely or maybe try to keep this one for a year until my contract runs out and deal with the lock screen problem.
skomes said:
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
2. Is there a performance difference between JB and ICS on the Cappy?
3. Should I go with a built-in kernel or flash a separate one?
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
5. I read on another post on the front page that the JB/ICS ROMs also use the internal SD card, mine is mostly full at the moment, how much space do the new ROMs take up?
Thanks for any help. Been considering flashing for a year but my phone recently got the lock screen button stuck problem and now I'm at a crossroads, either I buy a new phone entirely or maybe try to keep this one for a year until my contract runs out and deal with the lock screen problem.
Click to expand...
Click to collapse
1. In my experience multitasking isn't a problem on either but I don't open a lot of tabs in my browser so could be different for you.
2. If you want good clean performance go with ICS. Jelly Bean roms are still more or less in beta.
3. As far as kernels go stick with the kernel built into the from unless it instructs you otherwise. Or if you are looking for some feature that one kernel offers that another doesn't.
4. Read, read, and then read the instructions again for whatever rom you are going to and follow them. Depending on where you are starting from you may have to do different things.
5. I've personally never paid attention to how much it uses the internal SD if at all. I do know that some ICS and Jelly Bean roms have potential to format your SD card during the flash so make sure you do a backup before moving forward.
When you say the lock screen are you talking about the power button? If yes be very careful moving forward with any flashing. I say that because the power button is used to put the phone into recovery. There are other methods to get into recovery but they don't work for everyone.
Sent from my SGH-I897 using xda app-developers app
m1batt1 said:
1. In my experience multitasking isn't a problem on either but I don't open a lot of tabs in my browser so could be different for you.
2. If you want good clean performance go with ICS. Jelly Bean roms are still more or less in beta.
3. As far as kernels go stick with the kernel built into the from unless it instructs you otherwise. Or if you are looking for some feature that one kernel offers that another doesn't.
4. Read, read, and then read the instructions again for whatever rom you are going to and follow them. Depending on where you are starting from you may have to do different things.
5. I've personally never paid attention to how much it uses the internal SD if at all. I do know that some ICS and Jelly Bean roms have potential to format your SD card during the flash so make sure you do a backup before moving forward.
When you say the lock screen are you talking about the power button? If yes be very careful moving forward with any flashing. I say that because the power button is used to put the phone into recovery. There are other methods to get into recovery but they don't work for everyone.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I guess that is a good point. My lock screen buttons works but not 100% of the time. Originally the problem hit and it didn't work at all, now it works probably 70% of the time. I didn't remember that I would need it to get into recovery. Maybe I would need to buy a jig, but I guess I should flash now in case it stops working entirely down the line.
I'm also considering buying an S3 but it is quite expensive, at least $620 for it unlocked.
I had wanted to jump into JB because I was looking for decent performance and I don't think I'll be flashing a ton. I've got like 80 apps, tons of home screen stuff etc. that I don't want to restore many times. I just figured if JB is faster, I'd rather go with it.
Thanks for the helping me out.
A jig isn't the best bet because it forces it into download mode. If your button is currently working go for it. Jelly bean roms will eventually be the best thing out there but most of the roms for it haven't been perfected yet.
I have been on everything from 2.1 and up and I can tell you ICS is the best stable thing out there. At least in my opinion.
Sent from my SGH-I897 using xda app-developers app
skomes said:
I guess that is a good point. My lock screen buttons works but not 100% of the time. Originally the problem hit and it didn't work at all, now it works probably 70% of the time. I didn't remember that I would need it to get into recovery. Maybe I would need to buy a jig, but I guess I should flash now in case it stops working entirely down the line.
I'm also considering buying an S3 but it is quite expensive, at least $620 for it unlocked.
I had wanted to jump into JB because I was looking for decent performance and I don't think I'll be flashing a ton. I've got like 80 apps, tons of home screen stuff etc. that I don't want to restore many times. I just figured if JB is faster, I'd rather go with it.
Thanks for the helping me out.
Click to expand...
Click to collapse
I've run a rooted 2.2, a rooted 2.3.5, and a few different ROM's, I find that the easiest to use so far is JB, depending on the ROM itself you may run into a few issues with battery drain, but it's not horrible. Multitasking is fine, but I have OS monitor and a RAM booster for quick mem clearing. The only problems that I've ran into with JB ROM's is that you have make sure the internal memory card is backed up, otherwise you'll lose everything you have on it.
I too have thought about getting a SG3, but after flashing the JB ROM, I think I'm satiated until I absolutely have to upgrade my phone.... meaning I'm probably going to stick with this one for another year or so depending on if I'm able to keep it in decent enough shape. For the CM10 ROM's, they've removed the /datadata folder so that may affect slight performance. I got used to it after flashing a ROM that kept the /datadata folder and noticed that it wasn't giving me enough space to work my usual programs on a consistent basis. But overall I'm content with the ROM I chose and the performance so far.
You can always do adb reboot recovery
Sent from a jelly bean
korockinout13 said:
You can always do adb reboot recovery
Click to expand...
Click to collapse
That is true but adb wouldn't help him much if he's stuck in a boot loop. That's when a functioning power button is important.
Sent from my SGH-I897 using xda app-developers app
skomes said:
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
Click to expand...
Click to collapse
According to my expirience, ICS much better in multitasking, comparing with GB. ICS kernel consumes less RAM and more stable.
skomes said:
2. Is there a performance difference between JB and ICS on the Cappy?
Click to expand...
Click to collapse
JB for cappy is not stable yet.
skomes said:
3. Should I go with a built-in kernel or flash a separate one?
Click to expand...
Click to collapse
If you a going to install CM or AOKP, you defiantly have to install custom kernel. You will also have to install custom baseband (modem). I suppose, same goes to other roms.
skomes said:
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
Click to expand...
Click to collapse
Yes. RTFM for the rom you are going to flash. You will have to wipe data and cache, and maybe update bootrom.
I am reading stuff, but a lot of guides say 'Coming from GB' BUT they DO NOT say 'coming from stock', so I wasn't sure if those guides were applicable.
Will CM10 wipe my SD card?
Thanks for all the help so far. Going to flash within a couple of days.
I was figuring Helly Bean but most of the JB roms want you to flash CM10 first anway, so I'll try that out.
^
See TRusselo's Flashin Guide for assistance... http://forum.xda-developers.com/showpost.php?p=19425513&postcount=1
Sent from my SAMSUNG-SGH-I777 using xda premium
Tried following that guide.
Heimdall links are all dead.
Opened Odin, downloaded speedmod kernel, figured I'd install it, then download the rom to SD card and go. I was pretty sure speedmod works with stock Captivate.
Flashed speedmod and now my phone is stuck on the Galaxy S boot screen.
So yeah...that sucked.
Now I'm trying to restore stock with Odin but the instructions don't even say how.
Yeah this is why I don't see myself flashing very often...
And that guide needs more detail.
Ok, well I managed to install CM9.
I'm going to stick with it for now because a couple of you guys warned me off of Jelly Bean.
skomes said:
Ok, well I managed to install CM9.
I'm going to stick with it for now because a couple of you guys warned me off of Jelly Bean.
Click to expand...
Click to collapse
I'm currently on the 8/13 nightly build of Helly Bean (http://forum.xda-developers.com/showthread.php?t=1783064)
I can say that this particular ROM is ready for use as a daily driver. I've been using it for about a week now and haven't experienced any problems.
With that said, it is important to note that as said before, JB roms are still in beta, including this one. Also it is important to say that I did a completely clean install of this particular ROM (Factory data reset, wiped cache, wiped dalvik cache, etc).
Just thought I let ya know that not all JB roms are scary right now. If you're interested in possibly flashing it, here's the official website: http://hellybean.site11.com/index.html
Don't forget to backup your /EFS folder though, recently some people have had problems with their imei being switched, but this is easily avoidable if you take the proper precautions. Other than that, this ROM is great.
Yeah, I actually mentioned Helly Bean on page 1, it was the JB rom I was considering because it was getting rave reviews.
I had a scare last night about my IMEI then I remembered my IMEI doesn't match my box because it was warranty replaced with a refurb for the shutdown issue, lol, I was freaking out but good thing is it made me backup the EFS folder.
Thanks for the support.
I'll give Helly Bean a try in a bit, I hear it is very snappy and I'm excited about that, coming from stock Gingerbread, I really appreciate an OS that doesn't run like crap!
Does Helly Bean wipe your internal SD card? I was searching for that and couldn't find anything, so I think that means no, but wanted to make sure!
skomes said:
Does Helly Bean wipe your internal SD card? I was searching for that and couldn't find anything, so I think that means no, but wanted to make sure!
Click to expand...
Click to collapse
As with any custom ROM there is a potential for odd things happening on one phone that doesn't happen on another. With that being said I flashed helly bean and it didn't format my SD card nor has it effected my efs folder like some people have had trouble with.
Your best bet is to backup everything important to you and the operation of your phone prior to flashing just to be safe.
Sent from my SGH-I897 using xda app-developers app
Backup your efs folder before flashing anything
A few questions before I try Helly Bean, I noted that the kernel is separately available on the download site, am I supposed to flash it separately or is it included with the ROM? The flashing guide doesn't say anything about flashing a kernel.
And I should be able to flash it directly from CM9, correct?
Also this ROM is a lot bigger than CM9, 180MB vs 300MB, does that mean I have far less internal SD space available?
skomes said:
A few questions before I try Helly Bean, I noted that the kernel is separately available on the download site, am I supposed to flash it separately or is it included with the ROM? The flashing guide doesn't say anything about flashing a kernel.
And I should be able to flash it directly from CM9, correct?
Also this ROM is a lot bigger than CM9, 180MB vs 300MB, does that mean I have far less internal SD space available?
Click to expand...
Click to collapse
Answering my own questions in case other people need help.
Yes
Yes
No
I installed Helly Bean but for me, it is laggier than CM9 so I am disappointed.
Hello everyone. I received my Verizon SG3 shortly after it came out. I have been doing reading as I am very new to android. This is my first android phone. Previously I had an EnV Touch. Hated that thing, but it did the job. So any who I now have this awesome kick butt phone and it has all the Verizon crap on it I cannot get rid of. I have rooted and the bootloader is unlocked. I used a windows program to gain root and then used EZ unlocker to unlock the bootloader. I have been looking and looking to figure out what rom I want to start with, I want JB, but don't want a lot of bugs ATM as i don't have all that much time to play with flashing and being still so new I don't want to end up with a brick. I tried my harderst to figure this out by reading, but the info seams so spread out, I kinda want to try the CM10 9-6 as I have read it is stable and not many bugs. My main question is about kernels. Am I correct in thinking they will get flashed just like my rom will in ROM manager? Or do I need to flash through CWMR? How do I know what Kernel to use? I have been reading the CM10 takes a different kernel than say synergy or stock. Or will the stock kernel work till I load the proper kernel. If I knew about the kernel and how vital it was to go with the ROM maybe I wouldn't be so paranoid. I have a friend with a GS2 and he told me the kernel has to go with the ROM and if the two don't mach then you could brick. I can't afford a brick my first time around.
If you could give me some advice or point me in the direction of some more reading that would be great.
Thanks
JB
All ROMs come with a kernel in them. Typically you just stay with it unless you want some extra features or what not. There are aosp kernels and kernels based on the stock firmware. If you use a touchwiz based rom you need to use a touchwiz kernel.
I don't think it will brick it if you interchange them. It will just boot loop
Edit: you flash kernels in recovery just like a rom. if you change kernels without changing roms you need to wipe cache and dalvik cache through recovery also.
Sent from my Nexus S 4G using xda premium
Back up your IMEI before flashing anything, alot of horror stories floating around. Development has some fantastic guides. After that, most of the "big gun" rom's here have kernels, and are for the most part consistently the same flash method through recovery. Cwm recovery is solid and reliable, start with that until you feel comfortable enough to venture off. Make sure it's version 6.0.1.2 (regular or touch) for any jelly bean based rom.
Sent from my SCH-I535 using xda premium
I backed up the IMEI with the terminal emulator. So if the error occurred it would restore with the proper IMEI. Should I back it up any other way too?
Also I'm planning on using the Rom manager to flash the Rom. Do you not recommend that or should I do it manually with CWRM?
Thanks for the replies. I'm still getting my feet wet and know all about searching before asking. Used to program dish.
Sent from my Galaxy S3 using Tapatalk.
Your call, depends how paranoid you are! I would flash manually, it's a control thing for me, I know what/how/when all was done. Using 6.0.1.2 touch is awesome, speeds flashing up considerably.
Sent from my SCH-I535 using xda premium
I might have to try the touch. I have standard 6 on there. The one you listed. Rom manager gives me the option to load touch too. Friend uses Rom manager on his s2. Looks to just automate things a little.
What I don't know is if it wipes the appropriate areas first for a clean install or if it's doing it dirty.
Sent from my Galaxy S3 using Tapatalk.
Use the Synergy backup. If you lose your IMEI you just flash it again and it's back. Just make Nandroid backups and flash away. This is my first Android phone too and now I get why people become flash addicts, it's amazing what you can do. It's easy to relock and unroot if need be. Everything is easy if you take it smart and slow.
Sent from my SCH-I535 using Tapatalk 2
Here here!
Sent from my SCH-I535 using xda premium
Just stick to a couple rules and you will be fine. First is backup, backup and backup before flashing. Always stay within the Verizon SGS3 section, Sounds simple but others have made the grave mistake. When flashing kernels, stick to the software, ie flash a JB kernel to a JB rom, flash a ICS kernel to an ICS rom. You should not have any problems but if you do you always have a backup. There are many roms, just flash an try them, make sure to read through the threads to identify any issues that have been discussed. JB roms there are a couple, a TW based JB rom from a T-mobile leak that was ported to VZW SGS3 that works well, there are official and unofficial JB vanilla roms, ie CynogenMod. Stick to those rules, keep a back up, i usually will transfer a copy of my original backup to my pc just in case, and always backup to external sd card. Good luck and have fun.
You can also flash kernels via Odin I believe.
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!