I couldn't post in the development thread but thought this post might be helpful to a lot of people.
Now I could possibly be wrong about this, but if I am correct; all ROMs that are up to date currently are all synced to the stock CM10 Gerrit picks. Now having KTweaker is a very nice function; (With UV and OC), but since it is technically "out of date" there might be some instability. Another case of matter, Undervolting and Overclocking can cause issues depending on the hardware of your phone. Settings that should be able to work with MOST phones are posted in the OP. (First page.) If after those values you are getting reboots, you can try to increase the values to see if that helps in any way. Otherwise, if they are happening too much I would recommend sticking to the stock CM10 kernel. Even though the kernel is flashed by stock when first flashing the ROM, if you would like to re-flash the stock kernel you can download it from Task & Ktoonesz ROM in the OP. Make sure to give thanks to them as they are very helpful and as opposed to dealing with questions on the regular hopefully this post helps answer some. Thanks for the great ROM by the way guys. -
On another note, I am using this kernel with AOKP and have yet to run into any issues thus far. I am not sure if you have tried this, but you can try the settings on the OP for good performance/battery life but not without clearing/wiping the phone properly. I understand some people hate full wiping but I find it to be necessary before reporting anything not functional. If you haven't done this and I quote from everyone who has said this and posts that recommend this process.
(I personally only recommend doing this after charging your phone to 100% to avoid draining issues.)
After download of latest ROMs/Kernels:
Reboot to recovery
-Wipe Data/Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
-Wipe Battery Stats (Optional) (100% battery recommended.)
-Flash ROM
-Flash 7/26 Gapps package (Most stable as opposed to customized packages such as Inverted Gapps)
-Go to advanced settings once again.
-Reboot RECOVERY.
-Flash Kernel
-Wipe Cache & Dalvik ONLY, once more.
-Finally, Fix Permissions.
-Main menu and Reboot System.
Sent from my T&K Blessed SGH-I747
jaysoblitzed said:
.
(I personally only recommend doing this after charging your phone to 100% to avoid draining issues.)
After download of latest ROMs/Kernels:
Reboot to recovery
-Wipe Data/Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
-Wipe Battery Stats (Optional) (100% battery recommended.)
-Flash ROM
-Flash 7/26 Gapps package (Most stable as opposed to customized packages such as Inverted Gapps)
-Go to advanced settings once again.
-Reboot RECOVERY.
-Flash Kernel
-Wipe Cache & Dalvik ONLY, once more.
-Finally, Fix Permissions.
-Main menu and Reboot System.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Wiping battery stats is unnecessary on these phones because Samsung uses an automatic calibration.
meleii said:
Wiping battery stats is unnecessary on these phones because Samsung uses an automatic calibration.
Click to expand...
Click to collapse
Ah I see. That I was unaware of. Luckily I posted it as optional. I find my battery to last an extremely long time with heavy usage especially when listening to music and such. I have yet to encounter a problem so far. I also recommend to those who use it; to download flash player and use Titanium Backup to keep it easily accessible, since after flashing AOKP you lose the ability to download it from the app market by stock without changing the DPI. A lot easier for those who don't want to tinker with those settings.
Sent from my T&K Blessed SGH-I747
Related
Correct me if I'm wrong, here are some things I've been contemplating when flashing new kernels via the awesome app Kernel Manager.
I've found it useful to clear Battery Stats along with Cache and Dalvik Cache; I saw that Kernel Manager allows you to clear both Cache and Dalvik.
What are y'alls opinions on Battery Stats? Does it make sense to clear them out along with Cache and Dalvik when flashing a new kernel or is it just overkill?
Before I flash anything, I always wipe the cache & dalvik and yes, if I flash a kernel, I also wipe the battery stats. I want to make sure I get an accurate gauge of how my battery performs with the kernel I'm using.
posting & replying via the XDA Premium app
-----------------------------
axl409 said:
hi, just a simple question: what is the better way to flash a kernel? for now i do so:
-wipe dalvik cache
-flash kernel
-reboot
is the dalvik cache wipe a necessary step? if i don't do it, could been any error?
another question: i use nightly rom, and sometimes i also use lordmodUE kernel. the question is: when i upgrade nightly (i upgrade every day), i do this step:
-easy upgrade wipe
-flash rom
-flash gapps
-reboot
-then i go again into recovery
-dalvik cache
-flash kernel
-reboot
can i do so:
-easy upgrade wipe
-flash rom
-flash gapps
-flash kernel
-reboot
jumping the first reboot?
thanks all for reply
Click to expand...
Click to collapse
the reason why flashing is relatively complicated and requires so much process is to ensure that during the flashing process, every possible errors or elements that may contribute to errors are eliminated. the mix and matching of roms and kernels are literally endless, hence the possibility of errors such as boot loops and other issue can occur.
if it works for you it works, then stick with what you do. I generally always clear dalvik if applicable to your ROM. cache at times, should there be a large upgrade.
with what you had mentioned about cutting out the 2nd reboot, I generally did what you suggested when I was running CM7s and I didnt have any issues. hope that give you an idea.
-----------------------------
axl409 said:
hi, just a simple question: what is the better way to flash a kernel? for now i do so:
-wipe dalvik cache
-flash kernel
-reboot
is the dalvik cache wipe a necessary step? if i don't do it, could been any error?
another question: i use nightly rom, and sometimes i also use lordmodUE kernel. the question is: when i upgrade nightly (i upgrade every day), i do this step:
-easy upgrade wipe
-flash rom
-flash gapps
-reboot
-then i go again into recovery
-dalvik cache
-flash kernel
-reboot
can i do so:
-easy upgrade wipe
-flash rom
-flash gapps
-flash kernel
-reboot
jumping the first reboot?
thanks all for reply
Click to expand...
Click to collapse
Reboot your phone after you flash your custom ROM before you flash your kernel. It is known that you if you dont, custom kernel doesnt work properly. Its something to do with not letting your phone build the necessary files for your kernel. I guess thats why it takes longer for the 1st boot
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
dntesinfrno said:
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
Click to expand...
Click to collapse
Thanks man, will try your method and report back.
once you flashed your ROM(aokp) you need to reboot and let the phone fully boot into android... after that reboot to recovery and try flashing your Gapp + kernel
don't forget all the wiping and fixing permission for each steps
edit: wow this tab was open for a long time i guess. there was no other answer when i wrote this browsing through my opened tabs.
dingrn said:
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
Click to expand...
Click to collapse
Kevin my phone is exactly having the same problem did you come to a resolution
Especially on aosp roms it might help to flash the rom, let it boot once, then boot into recovery and flash kernel, wipe cache & dalvik, and fix permissions.
Also i've heard that some people will have alot of reboots before the kernel starts running smooth and stable. Or you could just have a bad phone that doesn't like to be tweaked. If i were you i'd take advantage of that warranty and try to get a replacement.
sorry for being a newbie....but what do you mean by fix permissions? =/
ohaai said:
sorry for being a newbie....but what do you mean by fix permissions? =/
Click to expand...
Click to collapse
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
jefferson9 said:
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
Click to expand...
Click to collapse
ive tried so many different methods of flashing kernels and all of them result in huge problems with crashes and random reboots all methods posted earlier are a gigantic fail. Im returning this refurbished phone for another refurbished and will report back
droidfta said:
Kevin my phone is exactly having the same problem did you come to a resolution
Click to expand...
Click to collapse
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
dingrn said:
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
Click to expand...
Click to collapse
hey had the same exact problem. Got a new phone under warranty cpu temps run lower and stable under current kt747 kernel I'll wait a few more days before underclocking but it's defiantly the phone you just got a weak cpu like I did
What is this?
Recovery flashable cache, Dalvik, and data wiping tools.
Why?
The script that wipes data should help prevent the problems experienced when different recoveries wipe data differently and with different options to choose from.
(Those that have typed in "YES" when wiping data know what I mean)
Why are there two?
One wipes cache & Dalvik.
One wipes cache, Dalvik, and data.
What data is wiped?
The data that is wiped should be all that is required for flashing ROMs (see below).
Media (your pics, music, etc) will not be deleted.
Feedback
Feedback from users that flash a lot of different ROMs (especially both TW and source built) will be useful in case there are any additional files and folders that need to be wiped.
Usage:
As always, flash at your own risk!
Flash in recovery
(these are most useful when using a recovery like TWRP where multiple zips can be queued for flashing)
A typical queue might be something like this:
1) Cache, Dalvik, and Data wiping tool
2) ROM
3) loki-doki
In case any devs want to add this to their ROM updater-script (most likely for an Aroma package), this is the code for the data wipe:
Code:
delete_recursive("/data/app");
delete_recursive("/data/app-asec");
delete_recursive("/data/app-lib");
delete_recursive("/data/app-private");
delete_recursive("/data/backup");
delete_recursive("/data/clipboard");
delete_recursive("/data/data");
delete_recursive("/data/drm");
delete_recursive("/data/log");
delete_recursive("/data/misc");
delete_recursive("/data/property");
delete_recursive("/data/system");
delete_recursive("/data/time");
delete_recursive("/data/user");
Download
Wipe_Cache_Dalvik_SGS4_v1.0
Wipe_Cache_Dalvik_Data_SGS4_v1.0
Wipe_Cache_Dalvik_Data_System_SGS4_v1.0
Thank you for this :good: what about formatting system though? Formatting system before a rom flash has solved many problems for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Planktron said:
Thank you for this :good: what about formatting system though? Formatting system before a rom flash has solved many problems for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
It would be redundant since all devs should format system in their install script.
Finally. :thumbup:
Sent from my SAMSUNG-SGH-I337 using xda premium
I have been meaning to thank you for this - I have used it a number of times already and found it to be very helpful. I am on OUDHS recovery - and while it would be better in some ways if I had TWRP because you can setup multiple files for flashing - it is still a big time saving tool when flashing any rom, update, kernel or theme on OUDHS/CWM. ANd it works beautifully.
I assume that I still need to wipe system when I want to do a totally CLEAN Flash - is that correct? If so - any thought of creating a third file that Wipes Data/Wipes System/Clears Cache and Clears Delvic Cache?
Or do you feel that is not needed?
Lol probably will implement this into my ROM once I put Aroma into it, if that's okay?
lol I love that part about "YES" i've seen too many users wipe their whole partiton and TWRP not be able to create one again (idk why) and then bootloops galore.
mocsab said:
I have been meaning to thank you for this - I have used it a number of times already and found it to be very helpful. I am on OUDHS recovery - and while it would be better in some ways if I had TWRP because you can setup multiple files for flashing - it is still a big time saving tool when flashing any rom, update, kernel or theme on OUDHS/CWM. ANd it works beautifully.
I assume that I still need to wipe system when I want to do a totally CLEAN Flash - is that correct? If so - any thought of creating a third file that Wipes Data/Wipes System/Clears Cache and Clears Delvic Cache?
Or do you feel that is not needed?
Click to expand...
Click to collapse
If devs are coding their install scripts properly, there is no need to wipe system (as I mentioned earlier with formatting system).
But...maybe I should make one just in case.
jetlitheone said:
Lol probably will implement this into my ROM once I put Aroma into it, if that's okay?
lol I love that part about "YES" i've seen too many users wipe their whole partiton and TWRP not be able to create one again (idk why) and then bootloops galore.
Click to expand...
Click to collapse
Absolutely you may use it. That's why I included the code.
Added zip to OP that will also format /system.
I wanted to thank you again for this tool - it has really been very useful and has saved me a ton of time and steps when flashing new roms and updates. Thanks - BIG TIME!
My phone has been running super laggy lately. Shiny ROM (CDMA) 4.4.2 Rooted. I tried clearing cache and davlik through CWM. Seemed to help for a few days. I usually only wipe cache partition and dalvik before flashing a ROM or something. Without that second step, what (if anything) does this accomplish? Any chance that this temporary lag reduction is a telltale for a particular problem I should know about.
Thanks!
Did you wipe data and system before flashing your rom?
Sent from my Galaxy Nexus using XDA Premium HD app
judson75 said:
My phone has been running super laggy lately. Shiny ROM (CDMA) 4.4.2 Rooted. I tried clearing cache and davlik through CWM. Seemed to help for a few days. I usually only wipe cache partition and dalvik before flashing a ROM or something. Without that second step, what (if anything) does this accomplish? Any chance that this temporary lag reduction is a telltale for a particular problem I should know about.
Thanks!
Click to expand...
Click to collapse
I've never found a convincing answer for your question. But from what I can tell a cache partition is probably meant to keep things the system uses closer at hand. Wiping it will force the system to create a new cache of things it needs and may possibly improve performance. However I believe the guys from google are good enough to keep a caching system that doesn't "age" (I mean it shouldn't slow down with time).
I believe the reason it should be wiped when you flash a new rom, is because a new system should create it's own cache...
Anyway, if I were you, I'd try flashing a new kernel. Personally I find Fancy Kernel to be the best. I've tried a few and they all let me down eventually. Fancy Kernel has helped in android 4.3 when my phone was getting extremely laggy with franco kernel. It was like buying a new phone.
I've recently used Dirty V that came with OmniMetal Rom and, although it was fast, it used too much battery. Once again Fancy Kernel helped with that issue and the phone is just as fast.