Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
henriqueberthem said:
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
Click to expand...
Click to collapse
Did you overclocked it? If you did - that is the reason.
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
henriqueberthem said:
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
Click to expand...
Click to collapse
Try using CoCore 8.2. And revert settings that you have changed to default and see what happens.
Deepsleep should be 3 or 4, on 5 it gives same result that you are getting. Freez and reboot on some time.
My deepsleep is "3".
henriqueberthem said:
My deepsleep is "3".
Click to expand...
Click to collapse
Then do first thing I told you before that. Without any customization, and with 8.2 version.
Ok, I'm going to flash to 8.2 cocore and keep the default configuration for testing
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
henriqueberthem said:
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
Click to expand...
Click to collapse
Try that newest.
8.2 was pretty good. No matter if it is old.
I tried the newest (Cocore E-v10) and still suffering from random freezes, causing the responses to touch are noticeably slower.
At this time I will flashing to version 9.6
Hello friend.
I tested the newest version of the kernel (refresh-r08 @ 14-Jul) and a few days ago that had no reboot.
But before I used the app tweek (cocore manager v2.1 or Kui) and believe they left is that my system unstable, because after that they uninstalled and I started to tweek the command promt using the Busybox my system has become lighter and reliable.
So it leads me to believe the problem was in the app customization.
Related
Normal: http://www.tabbal.net/files/Dragon-Kernel-Voodoo-v3.1.2.zip
OC: http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.1.2.zip
I rebased on the latest source from Samsung, JPX. Yes, it's still i9k based. Hopefully it helps a little with battery and such, won't know till it's been out for a while. The speedmod patch has also been updated, but the OC patch is the same. I also included my backport of the auto-group scheduler patch. So far, both of them are working well for me.
Both kernels are voodoo enabled and will enable voodoo if you don't already have it. If you don't want that, you need to install the voodoo-disable zip before flashing, or just put the disable-lagfix file in place before flashing. If you already have voodoo enabled on your phone, you do NOT need to disable it before flashing these kernels, as long as your current kernel has voodoo recovery (red Clockwork recovery), you are good to go.
Tested on Nero V5, but should work on other Froyo based ROMs as well.
If you are going to try the OC version, please download both of them and have the normal version ready, just in case. You can also use adb push from Clockwork if you can get it booted to recovery. Clockwork also has USB storage you can enable to be able to mount your phone's memory cards from a computer, so that you can put the non-OC version on there if you get stuck.
NEW for OC users.
The OC kernel defaults to 1Ghz. To enable OC, you can use the Voltage Control app that the OC ZIP installs for you. This is a MODIFIED version, so please don't update it. Load the app, then pull up the "states" drawer at the bottom of the screen. Select the frequencies you want to enable. Then set the "Limit clock to" spinner to set the max clock rate the system will use. You can change the UV settings if you like as well. To test, hit menu then apply for now. When you are happy, use "save as boot settings" and the system will set the frequencies at boot. I recommend you only change one thing at a time, and throughly test, before setting at boot. Bad OC/UV settings can cause all sorts of instability issues. Flash the stock clocked kernel if you get stuck, then delete /system/etc/init.d/S_volt_scheduler before flashing the OC kernel back on. That will force the system to boot limited at 1Ghz again. If you are so stuck you can't get to recovery, you can use download mode to apply a stock kernel with heimdall, just pull the zImage from the ZIP and flash that.
I'm not sure it will help anyone to post your OC/UV setup as every phone is different. But feel free to try it if you like. I haven't done much more than test that it can set the options and my phone is still running fine at 1280. I'll experiment with other speeds and such later.
Please note: Not every phone will work at any particular frequency. Many can run 1.4 just fine, others can't do much better than the stock 1Ghz. I recommend trying one step at a time, and testing throughly before setting at boot. Run some games and such to really push the system. I also recommend using only one or two OC settings enabled in the states. Every frequency step requires the system to notice you are asking for more CPU than the threshold, resulting in lag getting up to speed. I run with only 1400 enabled from the OC section and disable 200 just to speed up the transitions.
Changes from v3.1.1
Fixed sensors (auto rotation, auto dim screen, compass, etc)
Updated OC code to be more stable, courtesy of Morfic. Many thanks to him for providing code and assistance.
Updated Voltage Control app to reflect the standard voltages used.
My phone runs stable at 1.4Ghz now.
Changes from v3.1:
Fixed Mobile AP on Bionix V.
Changes from v3.0:
Updated speedmod patch to k12p
Updated Voodoo Sound to V2
Credits:
Speedmod patch from here: http://forum.xda-developers.com/showthread.php?t=822756
OC patch from here: http://forum.xda-developers.com/showthread.php?t=822027
Supercurio for voodoo and voodoo sound
Sweet!! gonna test it out now..thanks for this!!
Downloading now
THANK U!! flashing right now (normal version)
just flashed it and for some reason screen looks dimmer (to conserve more battery i guess??) or is it just me? one more thing speedmod is not really necessary right?
So this thing helps with battery?
Sent from my SGH-T959 using XDA App
downloading now...was just thinking about flashing the new trigger rom from Einherjar to try it out....will flash this with it and report back any problems
Been running the OC kernel at 1280 with CFQ, everything runs smooth and lightning fast!! Not one reboot or freeze up. Linpack is in the 20's. Thanks again T!!!
Edit: had this running on my phone for almost 2 hrs
KA6 DeOdexed
Will this work on the KA6 DeOdexed leak rom with voodoo lagfix enabled?
So far, so good at 1.2
Nicely done. I had 2.7 for a few hours and it kept freezing up. Hope this is the sweet spot. Just for clarity, the only difference between "apply for now" and "save as boot settings" is that the settings will need to be re-done when rebooted? Sorry if that's a completely "duh" question. One more: having the Voltage Control app now, is it recommended to freeze or uninstall Set CPU, or does Voltage Control trump Set CPU, or, vice versa? I notice the main screen does theoretically allow the slide bar to go to 1.4. TIA...
It's running great. At first, it got stuck while flashing the kernel and I had to odin back but it's fine now.
As far as battery life is concerned, it has only been about two hours so I can't say. The kernel itself has voodoo sound v2 so even ttabbal hasn't had it for long (as that JUST came out) so no one will know what kind of battery life the phone has.
On a side note: ttabbal: Did you get my PM about the FM radio? Is the module loaded trying to access the non-existing hardware? I wonder if that is what's killing the battery on the non-vibrant kernels. (Doesn't the 959D also have a FM radio?)
I tried to push it to 1400 with cfq but got a freeze up instantly. Went back to 1280, now everything is running smooth again. One thing I noticed though, my wifi is broke
My wifi is working...did yours stop working after you pushed 1400?
w00t! thanks ttabbal for being the Dev to provide Voodoo sound!
Mine stopped at 1.4 too. But right now im running 1.2 with 25 under. 25 under on 1. 50 on most the others except 100 which I went 75 under. Right now its really stable and fast so ill leave it like this for boot and try other stuff with the apply now. Hint only hit on boot if its 100% stable. Be careful with setcpu too.
Sent from my SGH-T959 using XDA App
Fedburin said:
My wifi is working...did yours stop working after you pushed 1400?
Click to expand...
Click to collapse
Yeah..noticed it stopped after I pushed 1400.. So be warned
love your kernels. i will have to donate again
So does this kill the wifi hardware at 1.4? If so, ttabbal has to modify the first post. (Or I will do it if he doesn't and we start getting more people complaining.)
On another note: Voodoo sound = gooooooood
Anyone else notice the automatic brightness setting is WAY dark? I've been running the T959D dragon kernel and this one is alot darker by default.
Thanks for the heads up.
Sent from my SGH-T959 using XDA App
bahnburner said:
Anyone else notice the automatic brightness setting is WAY dark? I've been running the T959D dragon kernel and this one is alot darker by default.
Click to expand...
Click to collapse
yeah, its the new version of speedmod that he incorporated, link to that thread is in the op
Probably is something on my Nook Color. But since I upgraded yesterday from 41 to 7.0.2 there is noticeable degradation of youtube videos playing on the default browser. Used to be fluid now is very choppy.
About the NC
Stock ROM 1.20 (upgraded yesterday)
CM 7.0.2 (from SD using Verygreen's instructions)
NO other kernel changes
EDIT: I think I confused everyone on my post..
I meant that I kept the NC stock ROM and upgraded to the new one (1.2) released by B&N on 4/25
The NC is running CM 7.0.2 from uSD without kernel changes. CPU settings: Performance. Max: 925Mhz
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
There's a 1.3 kernel??? Dalgrin's? Where?
silentbushido said:
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Click to expand...
Click to collapse
shawn605 said:
There's a 1.3 kernel??? Dalgrin's? Where?
Click to expand...
Click to collapse
Kernel Manager app
Do not set the overclock on boot until you know its stable.
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
LBN1 said:
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
Click to expand...
Click to collapse
The 1.3ghz is ready to release. It is just a matter of whether your Nook can handle the overclock or not. It should boot regardless though. The overclock is not set until after the OS boots to UI.
did you have OC before installing 7.02? installing 7.02 resets your cpu back to 800 MHz, and you need to reinstall OC kernels to get it back to what you had before
lanzagas said:
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
Click to expand...
Click to collapse
Been using the 1.3 oc kernel flashed through kernel manager. Seems to be working fine at 1.3 with oc set in cm settings.
No YouTube issues for me on new cm7.
Loving my week old nook color so far.
Sent from my HTC HD2 using XDA App
I didn't have a OC kernel before nor after.
I was using CM7 CPU settings. Max:925Mhz.
I had the 1.1 stable overclock before and currently am using it again. When I added the 1.3 uimage onto my Nook and tried to reboot, it stopped before the CM7 logos popped up. Blank screen with a "-" cursor and that's about it.
Glad to hear it is almost ready to be released, and will certainly try it again.
Oh, thanks Dalingrin for all your hard work on the kernels!
I just flashed nighly 20 ont my p970 and everything seems to be all right. Then i restarted, went back to CWM and flashed v08 nova script. Since that (about 25 mins) my phone is stuck at the LG Logo... Hope any1 has got a solution for me
maybe you should pop out the battery and try again
it happens in v06-v07 as well
if you stuck again,it definitely a bootloop
try the unbrick method
I already got nightly 20 back on my phone and also tried the updated version of the kernel... also tried to update with davlic and battery wipe and without, what else could it be?
Strange, especially as it seems to work for others with this combonation as well...
Same here. Nova v8 stuck in lg logo. I tried remove battery but didn't work. I boot it into recovery and flash CM 20 and nova 7 again.
Enviado desde mi LG-P970 usando Tapatalk
Wow, it's very strange for me if what did happen to you was true, 'cause I'm using CM7-Nightly#20 and Nova v08 Kernel well.
These are steps I've just done:
- Download the kernel then copy it to sdcard.
- Do the davik-wipe. You can find it in the advance of the Recovery menu.
- Flash the CM followed by the Kernel.
- Turn off instead of reboot the system.
Done. I waited for a few mins, then booted my phone. Everything are going fine still now. That is a battery friendly when cost only 2% after 4h.
I also got it to work soon after i posted this, but i had to sleep then and i was busy until now... But the problem was that there were/are different versions of the kernel and 1 of them doesnt seem to work with #19 and #20 nightly, as i tired both, but the nova v08-test1 worked like a charm and is battery saving as hell and i like it VEERY much! even though i am a bit confused that in cpu spy there are only values for 800, 1000 and deep sleep mode. but many others already reported this, so it either is a program bug or really a bug in the governor. Maybe I'll try another one tomorrow and report if this bug still exists But as long as battery drain is ok, i will keep lionheart, as it seems pretty fast to me.
One more thing i noticed is, that even though u set the CPU speed to a lower lvl like 600 it still seems to be set to 1000 according to cpu spy... Anyone else who also experianced this?
Nice work anyway guys and a big thanks
yes , agree, this combination kills your battery deadly
Not for me, installion went all fine. Did not reboot, but shut down instead, waited a half of a minute, then started. And performance is great, and battery got thru my day with 1+ hours of gaming and 3g+mobile network on all the time. (Left with 27% after 10h since unplugged the charger, that's fine for me)
N00BY0815 said:
I already got nightly 20 back on my phone and also tried the updated version of the kernel... also tried to update with davlic and battery wipe and without, what else could it be?
Strange, especially as it seems to work for others with this combonation as well...
Click to expand...
Click to collapse
I used CM7 #19 (as #20 has some bugs when someone calls you) and the latest Nova v08 and it worked for me. You just have to take out the battery after the first boot (if stuck on LG logo) and you should be ok.
P.S.
Another dev (aprold) is now working on Nova and he added some updates/changes on it. You might as well check on his latest post.
http://forum.xda-developers.com/showthread.php?t=1276645
I use cm7#20 and last nova08. My OB works fine. Very smooth. I'm pleased with this kernel. I think CPU spy has bugs. Lionheart os ok.
Sent from my LG-P970 using XDA App
Hi to all.
I`ve just flashed nova kernel v09. It's great.
Here I send you results of nova kernel v09 in CM7#20
Lionheart now true correctly working
Quadrant score.
I`ve forgotten
I didn't run nova script yet
Benchmark results without nova sctript.
Many Thanks to Aprold and knzo.
I still can't write on Development forum.
model: SGS international GT-I9000
due to corrently hot topic ICS on air everywhere
so im going go give it a try
at the first whn im on 1.12.30miui rom with glitch kernel, i upgrade to OneCosmic 2.11 with glitch kernel too, i realize that my phone is hot, after that i use all the check what happen with my cpu keep running on max speed for few hours for DRM, Media storage and download manager...
after 1day of using on 2.11 i feel like not hitting my target of lagfree, so im changing bk to miui 1.12.30 and after boot up, i get the same thing happen again, my cpu keep running on max speed for same, seem like it keep running on scanning media storage.
i just want to know why it keep running like thay, can anyone give me a answer? or is it because of gallery+?
SGS GT-I9000 OneCosmic latest build!
onecosmic is still in beta is not final ics so there's bug, because the cpu heat is forced because of such applications that are open gallery
c0c05 said:
onecosmic is still in beta is not final ics so there's bug, because the cpu heat is forced because of such applications that are open gallery
Click to expand...
Click to collapse
i dont think so...
when i change back to miui 2.1.13 im also having the same problem...
SGS GT-I9000 OneCosmic latest build!
Hi, as title, my Ace is running freaking slow, laggy and constantly reboot no matter what ROM I have used. I only hav about 30 apps in phone. Already used Class 10 card with Ext 4 partition but it still lag like crap (Link2SD). Anyway to solve it? I am nearly giving up on this phone already. Current ROM and kernel as in my signature. Some times the screen don't even wake up after I lock it.
-CPU max 800/ min 245, governor SmartAss H3, scheduler sioplus
*Waste of money invest so much on this
My friend you are using 4.2 and use 30 apps so it is obvious that you will have speed issues
Uninstall unwanted apps and then do a dalvik and cache wipe in link 2 sd
I think it would help
Also try pure performance or fly on mod and set governor to performance
soralz said:
Hi, as title, my Ace is running freaking slow, laggy and constantly reboot no matter what ROM I have used. I only hav about 30 apps in phone. Already used Class 10 card with Ext 4 partition but it still lag like crap (Link2SD). Anyway to solve it? I am nearly giving up on this phone already. Current ROM and kernel as in my signature. Some times the screen don't even wake up after I lock it.
-CPU max 800/ min 245, governor SmartAss H3, scheduler sioplus
*Waste of money invest so much on this
Click to expand...
Click to collapse
Android 4+ on our Ace is and will be laggy.
Go back to a gingerbread rom like The Ultimatum or Stocklite and you'll feel the smoothness
Sent from my GT-S5830 using xda app-developers app
Ok, if I go back to stock. The other custom kernel like psdna88 mem-mod and other Space Kernel does not allow me to install newer version of Busybox. How can I update it? Even the new one v9.9 (1.21.1-stericsson) has the option to remove BB from /sbin still cound't install
Why do you need the latest busybox ?
Sent from my GT-S5830 using xda premium