Has anyone tried this and know if this is a good combo for speed, battery, etc? And if I flash, should I flash the rom and the kernel at the same time or boot cr then reeboot and flash lk? Thanks to anyone who helps!:laugh:
rockingrubberducky said:
Has anyone tried this and know if this is a good combo for speed, battery, etc? And if I flash, should I flash the rom and the kernel at the same time or boot cr then reeboot and flash lk? Thanks to anyone who helps!:laugh:
Click to expand...
Click to collapse
It's what I use.
In twrp, I flashed cleanrom and then lean kernel and then rebooted my phone.
ROM kernel combo is very smooth and fast with best battery life. I stayed on WiFi all day.
Clean ROM 5. 6 le with lean kernel
Power saving mode is on.
2 hours and 33 minutes screen on time.
Just an average day on clean ROM.
I was streaming Pandora over 4g for a while.
sent from that young galaxy on clean ROM!
I haven't given any custom kernel a chance yet cos I been getting amazing battery life on the ICS OTA modem/rpm using stock kernel. getting somewhere around 5 hours screen on time!
lean kernel would be my second option for a custom kernel though, behind Ziggy.
http://projects.ziggy471.com/projects/ziggy471-sgs3-jb/files
http://imoseyon.host4droid.com/s3/vzw/#!/view=details/lang=en/sort=na
Related
how is everyone liking DAS bamf 1.7??
I think i am going to flash to it. i've been running 1.6.3 for about 3 weeks now and i like it and haven't had many issues (sometimes i need to shut down and restart my messaging service) but the battery life is reallyyyy bad... i have the extended battery and i haven't lost this much battery life with any other rom. before i rooted and flashed i actually was getting 2 days on the extended battery, it was really nice..
also i have a question, this is my first smart phone so im still new to this, a lot of people were saying that the imoseyons kernel was really helpful and i wanted to try, but i've never flashed a kernel... i was just wondering if there was anything i had to do to prepare to flash the kernel.
nope. put the kernel on the root of your SD card, go into recovery, and flash the kernel just like you would flash a ROM. quick n painless
I freaking love BAMF 1.7, so I would definintely say to check it out. Also, when you flash it, make sure you clear cache, do a factory reset, and flash using Clockworkmod NOT Rom Manager.
Just flashed BAMF 1.7 yesterday and its working well for me. Did a full wipe 3 times, bad habits, coming from BAMF 1.6.3. I am also running Imoseyons kernel on Normal Mode, InteractiveX Governor right now and the battery seems to be doing great. I use CurrentWidget to monitor my battery when I flash new things to make sure nothing funky is going on and it all seems to be working well
Its awesome with the urban theme!
Sent from my ADR6400L using XDA Premium App
awesome thanks for the info guys.
Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.
[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.
Doh! He said rectify lol
Sent from my Xoom using XDA Premium App
i am currently running cleanrom 5.0 and flashed the ktoonz kernal kt747 and needed help with the KTweaker app that was installed with it, im a noob with roms, kernels,etc.., ive been learning a lot and fell confident flashing and all but can anyone help me with the settings in the KTweaker app, im mainly looking for battery performance and this kernel was reccomended but after 1 day of running it my battery performance was horriable, thank you in advance for any help.
I'm on cleanROM 5.0 also. I tried the other kernals but ended up flashing the rom over again and kept the default kernal as I am getting great battery and performance. 14 hours and 19 minutes at 20% battery, with 4 hours of screen on time. If this helps any. I know you were asking about ktoons but thought I would give you this.
thanks i liked the battery performance on cr5 just fine, just was trying to get a little more, and like i said im still a noob can i dirty flash the cr5 or do i have to clear everything like when i first flashed rom?
All I wiped was both the caches and flashed the roms again. All my apps stayed. Everything works like a charm.
I want to flash this to my rooted but stock
I want to flash this to my rooted but stock phone... I have not changed recovery because I want the updates.... Is there a way to do this where I will continue to recieve ota updates.... totally updated at this point to jellybean... I kept having problems with roms and am sick of messing around with them.
Side note how is your reception after the last update .... mine pretty much sucks.
Thank you
russianlul said:
I want to flash this to my rooted but stock phone... I have not changed recovery because I want the updates.... Is there a way to do this where I will continue to recieve ota updates.... totally updated at this point to jellybean... I kept having problems with roms and am sick of messing around with them.
Side note how is your reception after the last update .... mine pretty much sucks.
Thank you
Click to expand...
Click to collapse
No you cant. And for the reception part there is nothing you can do other then flashing a ICS radio with odin but then I think your ota will fail too. http://rootzwiki.com/topic/34053-of...zon-sgs3-sch-i535-odin-or-recovery-flashable/
If you wanna flash a JB leaked radio (besides K3) then you will have to rock a custom recovery
I've had my phone up and running on AOKP Milestone 1 and a custom kernel (can't remember the name now) for a few months now. I decided to replace the kernel with Lean Kernel since my phone's been crashing recently, and it was mentioned that the kernel could be the problem (this thread: http://forum.xda-developers.com/showthread.php?t=1842971&page=135).
After installing the kernel and wiping the cache/Dalvik cache, my phone rebooted but would not let me past the lockscreen. I then pulled the battery and attempted to reboot into recovery, but now my phone won't turn on at all. I'm currently charging my phone but no light is coming on, so kinda worried.
Any advice/solutions would be appreciated!
EDIT: I should also mention that if I pull the battery and put it back in, I get a "battery charging" symbol on the screen for a few seconds.
Download mode?
Sent from my SCH-I535 using Tapatalk 2
Did you install the proper LeanKernel? If you are on AOKP milestone 1 that is 4.1 based. The newest LeanKernel is 4.2 based. Could be the problem. There are also distinctions between AOSP and TouchWiz kernels. Do you know which version you flashed?
Regardless, if you can get into download mode like hank said, you should be ok.
Can't Boot into recovery with three button method?
Tried getting into download mode?
Well I feel dumb but after some searching around, people recommended just blowing on the battery contacts. This solved it, so case closed! Thanks for all of the advice though.
And yes, the lean kernel was for TouchWiz roms, which got me into this mess in the first place.
So very recently my phone started to do things on its own. It starts pressing things on the screen randomly on its own, the screen locks up. I would have to keep tapping something to get it to work, or lock the screen with the power button, then unlock it to work, but then the issues comes back after a few seconds. Its rooted with Cyanogen 7 20130301-NIGHTLY, kernel 2.6.32.55.
I reset the phone to a fresh rom install, and the issues were still there. I changed out the battery, because I am suspicious that it is an issue with the battery or power.
Any help appreciated, thanks!
Flash a custom kernel. I never run CM7 with its stock kernel. The thing about the G2X is that every individual device is "different." My G2X handles the trinity kernel best, Mazout's kernel is great but gives me SOD's constantly, although I have not tested any of his latest builds since I only run ICS hack fests. I think flashing a new kernel would help you out a lot. I would recommend trinity (as they're my favorite), Mazout's kernel or Faux's kernel. In that order. I would also try over clocking and under volting when you get the chance.
Pain-N-Panic said:
Flash a custom kernel. I never run CM7 with its stock kernel. The thing about the G2X is that every individual device is "different." My G2X handles the trinity kernel best, Mazout's kernel is great but gives me SOD's constantly, although I have not tested any of his latest builds since I only run ICS hack fests. I think flashing a new kernel would help you out a lot. I would recommend trinity (as they're my favorite), Mazout's kernel or Faux's kernel. In that order. I would also try over clocking and under volting when you get the chance.
Click to expand...
Click to collapse
Can I flash the kernal while keeping the same rom and contents?
Yes. I would just clear the caches first. Then flash the new kernel
Sent from my Nexus 5 using xda premium
Ya I figured that out, I tried both trinity kernels and mazout, for some reason it would not boot up past the load screen. Not sure if I had to wait that long. I just went back to my nandroid backup, but for whatever reason the problem is not there anymore. I suspected that this was a hardware issue. Funny thing, my spare battery just broke down, it started to inflate. I need to get a new phone me thinks.
But now I am curious as to why I couldn't get the kernel to work. I would still like to do that. I even tried a stable CM7 rom and then flashed the kernels, still to no avail.
It takes a few minutes to boot up after you flash a new kernel because the system has to rebuild the caches.
Sent from my Nexus 5 using xda premium
Pain-N-Panic said:
It takes a few minutes to boot up after you flash a new kernel because the system has to rebuild the caches.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Few minutes does not mean over an hour does it? It just gets stuck at the boot logo for at least 45 minutes before I get annoyed and turn it off.
Lolol no!!!!! Few minutes means 5 at most lol. Are you sure you're flashing the correct kernel? Mazout does make more then one kernel. So does Trinity. Not trying to make you sound stupid or anything.....i just can't imagine why the kernel would cause the phone to freeze during boot.
Sent from my Nexus 5 using xda premium
Pain-N-Panic said:
Lolol no!!!!! Few minutes means 5 at most lol. Are you sure you're flashing the correct kernel? Mazout does make more then one kernel. So does Trinity. Not trying to make you sound stupid or anything.....i just can't imagine why the kernel would cause the phone to freeze during boot.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
I have asked about my problem here http://forum.xda-developers.com/showthread.php?p=49089235#post49089235
I got the correct kernel, just some weird issues, but some guy is trying to help me out.
Make sure to use the correct recovery. At least trinity is incompatible with CWM touch.
noobish comments:
-- As the story says, a kiss turned my G2X into an HTC Ruby!