Database Develop

Kernels causing reboots? Or is it something else

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.

[Q] Battery Life Miui vs Darky

Hey!
First things first, I've never had an android phone before so please keep in mind that I'm an absolute noob .
Basically, battery life is something important to me and would therefore like a recommendation between the two roms.
I'm currently on Miui 1.5.13 MCG2.1v and I'm not so impressed by the battery life. It barely lasts one whole day and the phone sits on my desk most of the time. I tried the suggestions from the Miui thread but I hardly noticed much difference.
I am also not prepared to make my phone even thicker with a fatter battery.
Despite loving the Miui interface and such, I will be prepared to switch to Darky's if battery life is much better.
A another small question, whats a good app I can download (Preferably free) which can help monitor the battery. For example, show how much % per hour the phone uses up.
Thanks!

Thats due to the fact MIUI is based of CM7 (CyanogenMod) which has battery issues but nevertheless 1 day seems a bit weird, with CM7 or MIUI the phone lasted at least 2 days with medium usage (gaming, benching, OCing, Messaging, surfing).
But even this can depend on the used Kernel. And Darky is based of the original Sammy Firmware which in case is more or less optimized for the SGS but i recommend a battery whipe after switching Roms.
And for Battery Monitioring Gingerbread (2.3.x) itself has this feature in the Settings under (About Phone -> Battery Use -> just click on the top Bar.

According to my phone settings, the kernel version I have is "2.6.35.7_platypus-miui-quorra-r9..."
If there is better versions of the Miui rom, I'll be willing to try it but if ultimately Darky's rom is the best option, I think switching to Darky would be the better idea.
As you can tell, I'm slightly confused on what to do next
Any input would be brilliant.

I have been on MIUI since RC3 - a few months back. any how since then battery life for me has improved drastically
i used to get about half a day, now i can get 2 days + if i use it minimally, or 1 full day if i use it excessively.
for me thats good i didnt get much better results using other custom ROMs, besides, there is not 1 single ROM out there that compares to MIUI so its well worth it for me

Try the TK-Glitch kernel... see if that's better for ya.

Prasad007 said:
Try the TK-Glitch kernel... see if that's better for ya.
Click to expand...
Click to collapse
forgot to add that !!
try a little undervolting with this kernel and that can also increase battery life

MIUI is very good indeed......on everything except battery life.
For battery life darky's rom is better for sure.

Thanks!
Okay, I'll try TK-Glitch's v10A kernel. Now for an even noob'er question , how do I install it
I figured I have to put my phone in to recovery mode and use odin3. If this is correct, why can't odin3 find the kernel I downloaded via PDA? I'm 100% positive its there or am I doing something wrong

tk glitch kernel is flashable thru recovery no need for odin

Done! annnnnnnnnnnnnnnnnd no service!

go into settings and system > mobile and network settings, and select use only 2g networks.
that should give u a signal, also check your IMEI number is not been changed.

Can't switch to 2g which I'm assuming, is because there is no service.
I tried to check my IMEI using *#06# and all I get is 'IMEI' and thats it. No number or anything

thats ya problem.
its easy to fix just restore the efs backup that you SHOULD of made when flashing MIUI
http://forum.xda-developers.com/showthread.php?p=14275826
you can also do it using root explorer

I have something called galaxy-efsbackup on the phone which I'm assuming is what your talking about?
So for clarification recovery mode, install zip from sdcard and choose the file?
Thanks for the help so far by the way

no that is the .zip file which backs up the efs, you should of applied that before flashing MIUI for the first time,
in result that would of left a folder on your sd card called 'backup' with a subfolder inside called 'efs' << that is what needs to be restored.
if it is not there, and you do not have a copy elsewhere, try to flash back to the version you was on earlier - or the kernel you used before this happened, that might sort it out.
however if it doesnt, you will need to flash back to froyo and start the whole process again it happened to me last week

Okay I have it
It has IMEI and Android sub folders within it with other files as well. What do I restore it?
Edit: I hope I needed to select back up and restore > backup because I accidently selected it. I have however copied the file "back up" on my laptop a couple of minutes ago before the massive **** up.
*Sigh* Sorry -_-

im confused as to what you have done lol
the nv_data.bin is what needs to be restored, use a app such as root explorer or similar
navigate to /system /efs ---> nv_data.bin <-- replace with the one on your sd card
reboot, Job done !!

I dont have 'ef' under systems
Should i just create one?

shizer said:
I dont have 'ef' under systems
Should i just create one?
Click to expand...
Click to collapse
my apologies. are you using root explorer or do you use another app
if using root explorer its just there on the first page, not under any / subfolder

Ah, I'm blind.
I've done everything and nothing. Didn't work
Everything in the ef folder hasn't been modified since I last rooted and installed the Miui rom.
help!

Gingerbread glitches? Android novice needs help!

So Bell Canada and Samsung both have terrible technical support.
My phone is i9000m, Bell Canada, running 2.3.3 (UGKG3). It had 2.2 in the box, and I upgraded through kies pretty recently.
Since the upgrade I have a few new problems that I didn't have before:
-GPS, which used to give me useful and reasonably accurate tracks for my walks and bike rides now spits out a bunch of garbage.
-Download mode still works, but recovery mode doesn't.
-Serious power drain under "Android OS." Upwards of 90% in an hour. Goes away if I kill "google services."

Do a factory reset if you haven't done one already. Most of the time that clears up any update bugs...
Sent from my GT-I9000 using xda premium

ccrows said:
Do a factory reset if you haven't done one already. Most of the time that clears up any update bugs...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
This did nothing for me except give me the headache of re-installing all my apps (again). Still no recovery mode, shoddy GPS, and crazy battery drain... oh and my bluetooth keyboard no longer pairs? What's up with that!?
Anyone have any other ideas???

New issue:
Market hangs at white screen after starting install on 10th app. Reset sometimes allows installing another one or two, but after that it'll hang again.

guardianfox said:
New issue:
Market hangs at white screen after starting install on 10th app. Reset sometimes allows installing another one or two, but after that it'll hang again.
Click to expand...
Click to collapse
Fixed, rolled back to previous version of Market.
New issue since another factory reset (2nd), 10 second delay between button press and lock screen.
I am sorely tempted to defenestrate my phone...

Why don't you flash a custom rom?
Sent from my Galaxy S using XDA Premium App

woolf clubs said:
Why don't you flash a custom rom?
Sent from my Galaxy S using XDA Premium App
Click to expand...
Click to collapse
If I could find a rom that fills all my needs better than stock 2.2, I'd be all over it. I have a lengthy list of requirements though, and warranty eligibility is in the top 3 (especially if I defenestrate the thing).
Can anybody recommend a rom with bluetooth working for wiimote and keyboards, netflix working smoothly (2.2 doesn't, stock 2.3.3 does), good power consumption, and stability?
In the mean time, I'm still dealing with the other issues outlined in this thread.

Flashing a custom rom would almost definately sort all your problems. As to which rom, you seem perfectly capable of reading. If you are worried about warranty, you can simply flash back to stock...........
Sent from my Galaxy S using XDA Premium App

woolf clubs said:
Flashing a custom rom would almost definately sort all your problems. As to which rom, you seem perfectly capable of reading. If you are worried about warranty, you can simply flash back to stock...........
Sent from my Galaxy S using XDA Premium App
Click to expand...
Click to collapse
For me that`s a last-ditch solution. I`m usually in a hurry when I break a phone and I`d want to be able to just plop it down at the bell booth during the work day, rather than taking it home first and flashing it (assuming it`s not broken beyond that point).

Hi,
I recommend you to try perform a Hard Reset with code *2767*3855# in dialer ( formats also your internal SD), flash the phone again (better with Odin) with a "standard" version.
Optional make a new Hard Reset (in special if didn't repartition the phone).
After that you can use a custom rom if you want. In past I used DocRambone rom, but now I preffer S.U.R.F.A.C.E. rom with Hardcore kernel and GO Launcher. GPS, phone, browser ....running without problems and battery keeps me over 50 h of medium use without GPS.

Tried hard reset and flashing the same stock 2.3.3 UGKG3 rom. No change. Still can't get into recovery mode, still crap gps, still 10 second lag between button press and screen on, still crazy battery drain.
Rolled back to 2.2, everything works except recovery mode and having weird problems with market imagining that I have apps I've never even looked at before and difficulty downloading. Market cache clear doesn't help. Hard reset doesn't help.
Upgraded through kies to UGKG3 again. Same problems as before, but market works at least. If no solutions available today, I'm taking it to Bell for service and maybe exchange. If that doesn't resolve I'll flash a custom rom.
DSGE said:
Hi,
I recommend you to try perform a Hard Reset with code *2767*3855# in dialer ( formats also your internal SD), flash the phone again (better with Odin) with a "standard" version.
Optional make a new Hard Reset (in special if didn't repartition the phone).
After that you can use a custom rom if you want. In past I used DocRambone rom, but now I preffer S.U.R.F.A.C.E. rom with Hardcore kernel and GO Launcher. GPS, phone, browser ....running without problems and battery keeps me over 50 h of medium use without GPS.
Click to expand...
Click to collapse

New update...
GPS borked entirely this time. Gets a fix, but the fix doesn't follow me. If I run My Tracks, it just stays in a 10 meter area while I walk in a 4km circle away from and back to that area.
guardianfox said:
Tried hard reset and flashing the same stock 2.3.3 UGKG3 rom. No change. Still can't get into recovery mode, still crap gps, still 10 second lag between button press and screen on, still crazy battery drain.
Rolled back to 2.2, everything works except recovery mode and having weird problems with market imagining that I have apps I've never even looked at before and difficulty downloading. Market cache clear doesn't help. Hard reset doesn't help.
Upgraded through kies to UGKG3 again. Same problems as before, but market works at least. If no solutions available today, I'm taking it to Bell for service and maybe exchange. If that doesn't resolve I'll flash a custom rom.
Click to expand...
Click to collapse

Phone was sent in for repairs and returned to me this morning. GPS still broken (completely, no signal period). Everything else seems fine.

the issues you are having suggest to me the problem is with the KG3 stock rom.
Before getting even more frustrated with both your phone and Bell, I would advocate:
1. do a complete phone clean with sd card reformat (sent you a pm with a link)
2. flash the stock JVR pda in odin and also flash the KG3 modem and CSC at the same time
3. you are then still on stock Samsung, official firmware and within warranty even if that firmware has yet to be released in Canada
4. then if you want you can still flash a custom JVR kernel and a custom JVR rom if you want to improve performance and/or alter features beyond stock

lgsshedden said:
the issues you are having suggest to me the problem is with the KG3 stock rom.
Before getting even more frustrated with both your phone and Bell, I would advocate:
1. do a complete phone clean with sd card reformat (sent you a pm with a link)
2. flash the stock JVR pda in odin and also flash the KG3 modem and CSC at the same time
3. you are then still on stock Samsung, official firmware and within warranty even if that firmware has yet to be released in Canada
4. then if you want you can still flash a custom JVR kernel and a custom JVR rom if you want to improve performance and/or alter features beyond stock
Click to expand...
Click to collapse
Thanks for your help. I'll look into it.
Before I do that, do you or anyone else have the stock settings under *#*#3214789650#*#* (AngryGPS)??? The settings for the SUPL Settings section are all BLANK!!! I can only assume the rest of the settings in AngryGPS are too. That seems bad.

Sleep of death in all ICS Roms

Hi. i tried almost all the custom roms. all were well. when i shift to cyanogen and miui and ics roms, i always get sleep of death issue or random reboot issue. Any fix for this ? is this because of Bootloader ? how should i get the info about my current boot loader. means whether i have froyo boot loader or ginger ?

majidshahab091 said:
Hi. i tried almost all the custom roms. all were well. when i shift to cyanogen and miui and ics roms, i always get sleep of death issue or random reboot issue. Any fix for this ? is this because of Bootloader ? how should i get the info about my current boot loader. means whether i have froyo boot loader or ginger ?
Click to expand...
Click to collapse
cant find this but you can flash gb bootloader it is backwardly compatible with froyo also

This is interesting... I've had sleep deaths on all of the ICS roms I've tried, coming from CM7 before that...
I have had no idea what bootloader I've been on, so I went ahead and loaded bootloaders from KF1. Couldn't even find KK4 anything... (most of the links in the forums are dead now)
I hope this fixes it up, otherwise I'm going to have to go back to GB ... (and I really don't want to...
Anyone come across a remedy for this?

I've had issues with the SOD, but, I've ONLY had it when I have been on GB bootloaders. My usual procedure for flashing ROM's is to FTS/MC to JF6(Eclair) then flash my ROM. So with ICS, I have never had it. I've run every THS, and ICSSGS ROM, WiUI, Doc's Master V5, and Fusion. Now with Fusion, it recommends GB loaders, so when I recently loaded it, along with the GB boots, I decided to stay with GB loaders when I switched to Doc's Master V5, I got a SOD 2 nights ago.
I also have to say that I did have SOD issues with EVERY GB Rom I ran, so i can say with a high level of confidence that it really has nothing to do with the ROM's themselves, and in my experience, has more to do with the bootloaders than anything else. I'm no bootloader expert by any means, but it's just my experience.

sleep death from poppies - yay
See OP of my ROM to avoid sleep death - it has settings.

Wow, The bootloaders have solved all my problems...
If anyone stumbles upon this in search of sleep death or charge death, (in my case both, would die after being charged over 90% and taken off the charger untill it got to around 80%)... GO HERE
Use the KF1 bootloaders with ANY rom...
It not only solved my charging / dieing issues but fixed my lag issues aswell. I can actually use my phone's browser again! (without wanting to throw it in the pool out of frustration)

What about people on CM9 based ROMS. The thread you liked to says CM users stay away in bold

ADDED:
MadGoat said:
A bit of an update,
After the bootloader update my phone acted fine for over 48 hrs..
HOWEVER, it is now back to its full charge, sleep death shinanigains.
The Bootloader's obviously did not solve the issue, however my phone (when its on) is quite a bit quicker and more responsive in all tasks.
I'm beginning to think that it might be a battery related issue, the phone (and battery) are now over 2 years old now.
The search continues...
Click to expand...
Click to collapse
Assuming your running a i897 bootloader now, (which means you DO see the AT&T when you boot and you DON'T see "galaxy s i9000" during boot)...
You can use this. I give no guarantee and I'm not responsible for anyone's outcome...
However, I can tell you I simply flashed this from the computer once I had done a cwm backup and pulled a copy to my desktop.
After it flashed,
I ran CWM,
flashed Icy glitch kernel (so I could reflash slim ICS),
rebooted to CWM again,
flashed my slimICS,
rebooted to cwm again,
cleared Caches and formatted all but the sdcard ... and restored my backup...
To help this process i would suggest creating a "Flash Folder" on your Internal SD. Categorize your rom / kernel / modem... what have you, will make life much easier.
Took a couple minutes to solve what I have been dealing with for a month...
All this being said, be sure you have the correct drivers for odin to see your phone. I needed to use Nexus S drivers, I assume because my rom (and subsequently the kernel) are nexus s AOSP...

I'm running dark knight 2 and have had no problems. I am also on GB bootloaders.
Sent from my SGH-I897 using XDA Premium App

Why 2? 3 is out and has so much customization now

i tried 3 and have had issues with signal that clear up as soon as i put 2 back on it. i have three stored on my phone to swap to at any point though. now that there are new nexus modems out i may try again but i am currently very happy with two. with the kf1 modem i have five bars all the time.
Sent from my SGH-I897 using XDA Premium App

UPDATE
A bit of an update,
After the bootloader update my phone acted fine for over 48 hrs..
HOWEVER, it is now back to its full charge, sleep death shinanigains.
The Bootloader's obviously did not solve the issue, however my phone (when its on) is quite a bit quicker and more responsive in all tasks.
I'm beginning to think that it might be a battery related issue, the phone (and battery) are now over 2 years old now.
The search continues...

yeah im been having a lot of issues with ICS ROMs on my captivate too. I just went back to GB today, cuz i cant take having so many deaths during the day....i wish there was a fix.

MadGoat said:
ADDED:
Assuming your running a i897 bootloader now, (which means you DO see the AT&T when you boot and you DON'T see "galaxy s i9000" during boot)...
Click to expand...
Click to collapse
Is this the definitive way to tell what bootloader you are running?
I think it's worthwhile to note that I have run a few ICS ROMs on my Captivate, usually charge it at night, and have never experienced SOD. Lots of people posting that they *do* experience it. I think the fact that some don't would be useful to whoever is debugging this issue.
I am currently running Docs Master ICS V5 Final w/ Glitch v14 B5 kernel.

I heard it has something to do with the CPU frequency setting. Once u raise the lower one, the DOS should be fixed.

My wife's cappy has does once in a while. She's only run cm7 with glitch. So I also will try raising min freq. From 200 to 400mhz. We will see what happens.

tommyguns818 said:
My wife's cappy has does once in a while. She's only run cm7 with glitch. So I also will try raising min freq. From 200 to 400mhz. We will see what happens.
Click to expand...
Click to collapse
How to do that? SetCPU or any other free one?

[email protected] said:
Is this the definitive way to tell what bootloader you are running?
I think it's worthwhile to note that I have run a few ICS ROMs on my Captivate, usually charge it at night, and have never experienced SOD. Lots of people posting that they *do* experience it. I think the fact that some don't would be useful to whoever is debugging this issue.
I am currently running Docs Master ICS V5 Final w/ Glitch v14 B5 kernel.
Click to expand...
Click to collapse
What was ur process of installing ur ROM. Maybe thats the trick. Mind sharing?
I usually do this:
1) Flash JF6 Eclair Odin
2) Master Clear
3) Flash GB UCKJ3 Bootloaders
4) Flash boog_KJ3_kernal3.tar using Odin3 v1.85
5) Flash CM9 (Goes into bootloop)
6) Re-Flash CM9
7) Reboot into Recovery and Flash selected ICS ROM.

After I posted about never getting an SOD on ICS ROM
argus1185 said:
What was ur process of installing ur ROM. Maybe thats the trick. Mind sharing?
Click to expand...
Click to collapse
Funny, I'm still new enough that I followed the directions on the OP for Doc's Master ROM:
"Installation:
-Firstly you must have rooted + CWM installed (you can flash over any rom)
-GB Bootloaders recommended...
-If lagfix enabled then disable it.
-Recommended removing external sd before flashing also.
-Copy rom to internal SD and Reboot into Recovery
-Wipe Data + Cache + Dalvik Cache
-Go "Mount and Storage" and format system
-Flash rom and reboot. At least 5 minute wait for first opening.
----if you get bootloop(probably you are coming a sasmsung based rom),remove battery, reboot into recovery using 3 button combo and reflash rom!
-When first opened let it at least 10 minute settle then reboot again...
-After second opening Enjoy your new rom..."

[email protected] said:
After I posted about never getting an SOD on ICS ROM
Funny, I'm still new enough that I followed the directions on the OP for Doc's Master ROM:
"Installation:
-Firstly you must have rooted + CWM installed (you can flash over any rom)
-GB Bootloaders recommended...
-If lagfix enabled then disable it.
-Recommended removing external sd before flashing also.
-Copy rom to internal SD and Reboot into Recovery
-Wipe Data + Cache + Dalvik Cache
-Go "Mount and Storage" and format system
-Flash rom and reboot. At least 5 minute wait for first opening.
----if you get bootloop(probably you are coming a sasmsung based rom),remove battery, reboot into recovery using 3 button combo and reflash rom!
-When first opened let it at least 10 minute settle then reboot again...
-After second opening Enjoy your new rom..."
Click to expand...
Click to collapse
Which GB Bootloader are you using?

[Q] Speedmod Kernel N7000 K3-6

Greetings,
Initially I wanted to post at the kernel release thread, but due to lack of 10 posts yet ( im still new ), I cant.
So my questions is easy, just need to be clarified.
1)I already flashed the kernel, it appear in the 'About phone' section. but i did not see any effect on the battery yet. Do i need to wipe anything first? Or the features of this kernel are already activated when successfully flashed?
2)If going to wipe, is this going to disturb emmc? I know MMC_CAP_ERASE is disabled, but i did not know the effect of wiping on this kernel yet.
Thanks a lot. Especially to Hardcore.

It could be, that you overestimated the effect of having good kernel on battery, the main battery eaters, when the device is used are screen, comm/sync functions, and active apps. So, I would not recommend wiping, unless you have some malfunctioning apps. Instead, check two threads: one by Entropy512 on battery drainers (I may try to find the link latter) and betterbatterystats thread. Armed with knowledge from there, you will be able to lower you battery consumption.
And, btw, this all does not mean that there's anything wrong with speedmod kernel, it's probably one of the best for stock ROMs.

IF you like me dont beleive the 3rd party programmers that the MMC_CAP_EREASE disabled that solve the bircking issue, you could flash abyss 4.2 then run jbdroid script (it is deleting the old kernel files wipe cache and dalvik cache) and then install the speedmod.
I simply can't beleive that mmc_cap_erase disable could solve the bricking issue until Sammy told us and they come out a solution.

sounds interesting. can s.o. confirm this?
I thought wiping cache/dalvik cache did not have any risk of bricking as long as you don't do a full wipe and/or restore of sw-bckp.

Running Speedmod K3-6
Hi,
I've just upgraded to K3-6 and currently on Kingdroid Notemania v 4.2.
Can't help but noticed that my Note gets heated up pretty easily. Plus, the battery can drop from 100% to 88% just by browsing through my Facebook and Whatsapping for less than half an hour. Previously when I'm on stock ICS running speedmod K3-3, my battery took about 10 minutes of browsing before dropping a single percent.
Any thoughts on this?
Tim