How to diagnose cause of extreme UI lag? - AT&T Samsung Galaxy S II SGH-I777

What I'm running:
Latest NEAK kernel + AOKP build 36.
Issue also occurred in Phonebricker + NEAK (sammy version).
My issue:
Occasionally the OS will get extremely slow, like you would expect if the phone were running at 100mhz or something. Everything continues to work, just reeaaallly slow. For instance, music playback gets very electronic-y as sounds are stretched out, tapping one of the capacitive buttons takes 5-10 seconds before vibration/feedback, and another 5-10 seconds before a menu pops up. I managed to get the NEAK configurator open and scrolled to the CPU tab, and it claimed I was at 1200mhz - though the phone didn't even get warm so I'm skeptical.
I'm guessing since I've done a full wipe between phone bricker + NEAK and AOKP + NEAK, the only thing in common are my apps and the NEAK kernel, so it stands to reason it would be one or the other causing this. My wife's GS2 is running AOKP + NEAK as well though and we haven't experienced this problem on it yet (but it's intermittent so it might be there, just hasn't happened yet). I'm currently running conservative governor + SIO, but it has also happened on conservative + NOOP.
While I could just change a bunch of sh!t and hope it goes away, I'm more interested in figuring out what's causing it, and fixing it properly. How can I figure out what's going on? What will log this kind of thing? What do you guys recommend?
Thanks!

this is really easy/simple. flash a different kernel. all devices are not created equally so you need to just try everything that we have and see which best fits your device.
if you had this issue on 2 different roms with the same kernel then you've answered this question in your post for yourself. it wasnt even necessary to post this dude. change kernels. done.
some phone like neak kernel, some phones dont. some phones like siyah, some phones dont. you cant "fix" that unless you get a different phone and try neak again. but even then it my not "fix" this issue because nothing is broken.

Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".

Eckyx said:
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Click to expand...
Click to collapse
If you're undervolting when this issue is happening, change it back to regular voltage.

I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium

Phalanx7621 said:
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2

Simba501 said:
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?

Eckyx said:
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Click to expand...
Click to collapse
Stock & Siyah. My issue with it wasn't major; it just isn't as polished as GB. The difference is noticeable.
Sent from my Galaxy S2

When mine gets laggy, I usually pull out the battery and put it back after 10 min or so. If you are leaving the phone on more than 2-3 days at a time, that could really hurt the memory and phone performance. The phone usually runs on 300 mb but it will run about 700mb ram after 3 days (even force closing everything).
It is not mentioned so I just wanted to cover all bases

After posting about giving NEAK another try, I did. And within 10 minutes got an extreme lag slow down while typing. Didn't touch any settings kernel side. So I flashed siyah kernel and so far no problems. Sux too. I liked NEAK.
Sent from my SGH-I777 using xda premium

I have been running Siyah with Task's AOKP and have had zero lag and great battery. No UV or OC.
Sent from my SGH-I777 using xda premium

Posted this in NEAK thread but also posting it here:
I just installed the new AOKP, used kernel clean script and installed NEAK 2.0.5x, then went into the NEAK Pro config and changed my governor to Conservative and sched to SIO. Rebooted, opened Scramble with Friends and immediately got superlag.
Turning off the screen and waiting 20-30 seconds fixes it (long enough for the phone to go to sleep), but nothing else short of a reboot will help. I can leave it like that for an hour (if I don't let it sleep) and it'll still be uberslow.

Related

[Kernel] StupidFast v1.2.3 (UV Test / No Voodoo)

This is an undervolt test version of my new StupidFast Kernel v1.2.3. This is a TEST release (NO VOODOO). This kernel aims to be fast, compatible, stable, and have good battery life. It is based on my StupidFast v1.0.36.
Code:
Changes since 1.2.2:
Fix for the 0.5-1.0 second pause/lag opening apps/drawer
Scheduling Tweaks
I/O Tweaks
Changes since 1.1.23:
Stock 1ghz @ 1225mV
Changes since 1.1.14:
Tweaked minfree settings
tweaked io scheduler
more compiler flags for cortex/hummingbird cpu
tweaked wifi scan interval to help with battery life
Changes since 1.0.36:
removed custom boot animation to trim size.
using kernel jhash3 instead of jhash2.
optimized compiler flags for the hummingbird cpu.
changed some kernel scheduling timings.
BLN disabled by default (configurable with [url=http://forum.xda-developers.com/showthread.php?t=823922]this app[/url])
You will see that the custom boot animation was removed. It's okay. If you already have v1.0.36, 1.1.4 or 1.1.23 installed on your phone, the animation will stay. If you're new to my kernels with v1.2.3, your old boot animation will be there.
I'm not seeing any lag on the phone. Gallery opens pretty much instantly. Settings->Applications->Manage opens pretty much instantly. Launcher Pro+ pretty much instantly appears when the phone starts up.
Testers could NOT find any audio problems with this kernel using the media player in JT's Clean ROM. I've tested Youtube and Pandora and have had no audio issues. Also, we couldn't find any issues with USB mount/unmount, settings changes, etc.
As always, if you find a bug or what you think might be a bug, let me know. This is NOT the final stable release of the 1.2 kernel. Stay tuned to #samsung-fascinate on FreeNode or @geeknik on Twitter!
Download:
http://dl.dropbox.com/u/6088006/stupidfast-test-v1.2.3.zip
saps from #samsung-fascinate said that v1.0.36 was "far and away the fastest real world kernels I've ever seen, period"
If you like my kernel, show me some love. Donate today!
Thanks to saps, jt1134 my beta testers and the kind folks that donated cash to the cause! Keep fighting the good fight!
sweet. dowlloading now.
Downloading also.
I like your kernels, but I just noticed I am getting a super weird output in ADB when I try using that. I also have superdark ROM so it could be either one.
Ok, I just rebooted and checked again and all is running fine with 1.2.2 in recovery, but not in running android system, must mean its the rom.
Downloading now.. went with full full wipe with jts clean, and still getting popping, on asop player, double twist, pandora
Besides the battery life which is supposed to be increased, is there any other benefit to UV ???? Longer processor life, runs cooler, etc.
What are the drawbacks, if any ???? Does performance take a big hit, etc.
I'm asking more in general terms. Obviously I will observe first hand with this kernel, which I'm downloading now.
mexiken said:
Besides the battery life which is supposed to be increased I assume, is there any other benefit to UV ???? Longer processor life, runs cooler, etc.
What are the drawbacks, if any ???? Does performance take a big hit, etc.
I'm asking more in general terms. Obviously I will observe first hand with this kernel, which I'm downloading now.
Click to expand...
Click to collapse
In theory, as I know computer not cell phone, UV will allow it to run cooler, which does mean last longer (but is that really a problem?) and use less juice while still being as fast as before. If it runs stable you will not see a performance hit and it will better with the battery. It will just freeze your phone if its too low and requires more juice, really no harm can be done, overvolting is more dangerous as that burns up cpus, but you overvolt to make the higher frequency stable. Simple overclocking principals apply, you want the lowest voltage for your cpu frequency.
spyd3r05 said:
Downloading now.. went with full full wipe with jts clean, and still getting popping, on asop player, double twist, pandora
Click to expand...
Click to collapse
are you upping the CPU to 200mhz to run those? I am doing that and its just fine, although I never had a popping problem at 100mhz either. I just set the min to 200 because that cleans up a little bit of the lag too.
Possibly related, every once and a while my phone will just decide to press a soft key on its own, what is that? (that causes a slight skip in the music when I am playing it)
destroyerbmx said:
are you upping the CPU to 200mhz to run those? I am doing that and its just fine, although I never had a popping problem at 100mhz either. I just set the min to 200 because that cleans up a little bit of the lag too.
Possibly related, every once and a while my phone will just decide to press a soft key on its own, what is that? (that causes a slight skip in the music when I am playing it)
Click to expand...
Click to collapse
see if listening to it while hooked to power recreates the problem... i noticed for me atleast its only when plugged in...
I have it up to USB and its not skipping or popping right now, I am also using mixzing
v1.2.2 is the least fastest of all the geeknik kernels for me. There is 1 almost 2 second pause loading and exiting apps unless it was already in memory.
Still faster then everyone elses kernel. And so far battery life looks to be way better on this one but I haven't had it long enough to say for sure.
Nothing has changed on my audio popping issues so I am still using SetCPU at 200min still. I am short 6 hours of battery life like this by my best guestimate... which isn't a big concern for me- just reporting for those who need to make it thru a day without a charger nearby.
Never had any FC's with USB.
Touchwiz/JT's Super Clean ROM
And a thank you to geeknik for all your efforts! love how your pumping these out!
Kernal runs great! No unwanted sounds from the stock music player in jt's rom. USB works just fine. Thanks for your hard work!
are you using setcpu? if so that helped me fix it bumping min to 200... any one else having the problem might try that...
Interestingly enough, this kernel does seem a touch slower than the 1.2.23 regular voltage kernel. Hangs just the slightest bit when firing up and exiting dolphin browser and xda app. Still, appears to be MUCH better with battery life, as the previous geeknik kernels were ravaging my battery.
Definite progress but not quite perfect imho. Still thanks for all your work geeknik, you're killing it with these.
Also fyi, running custom blackhole, with sns and lp
Sent from my StupidFast Fascinate using XDA App
This kernel is running fairly smooth, like the other 2. I can deal with the extra 0.5 second delay when first opening an app, as long as BLN is optional and battery life is extended. Thank you very much for taking the time to come up with these kernels for us. Other kernel providers tend to make their products less accessible for us XDA users, but you take the stress out of the search. Thank you again.
Thank you very much for taking the time to come up with these kernels for us. Other kernel providers tend to make their products less accessible for us XDA users said:
This is because these development forums are filled with junk threads, nobody taking the time to read a Lil bit. Its getting worse and devs leave because of it. Not the devs fault at all. Just a point to make: )
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Can someone explain how to get bln. I saw a post about it but can't find it or I'm over looking it like an idiot
Sent from my SCH-I500 using XDA App
zachsx said:
Can someone explain how to get bln. I saw a post about it but can't find it or I'm over looking it like an idiot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Re-read the first post of this thread, there's a link to how to enable/disable bln
The uv kernel is a winner of course. I test these kernels for geeknik before he throws them up for the masses. Not just running quadrant [although I do that too] but going thru the real phone stuff itself. The manage applications load, replacing new dock shortcuts, gallery, apps and stuff everything we actually want to see improve with.
I for one never had battery issues with previous stupidfast kernels but I know some did, same this music crackling. It seems to me most of you that do are either running blackhold or deodexed rom though and quite humbly I'd look their for your culprit moreso than the kernel. If there was a music skipping issue from the kernel itself it would manifest itself across the boards but it doesnt.
Anyway, battery life is going to be stellar trust me, under light-moderate use Im only using like 2% per hour here swyping 8-10 texts per hour here, very good indeed
Hey Saps- I see ya on all the forums and your contributions have really helped me out...
That being said I keep seeing an overlook of real world usage in these testings. Can you guys test beyond stock apps? I mean checking stock should be the first thing you do obviously but how many people use the stock music player or the stock browser, etc? I am betting most the people that have the knowledge enough to test these kernels and ROMs aren't using stock functionality and apps.
Please test this kernel with the PowerAMP or Music PlayerPro music apps before writing off the issue.
Use Dolphin to check the internet, etc. Use K-9 to check email, etc.. ya know- use the popular apps during testing also if you could?
Audio cracking, FC's with the USB settings, and I even heard mention of live wallpapers having issues. These reports coming from 3 reported different ROMs.
How are you missing this?
I myself have had great success with battery life on the Stupid Fast kernels. Better then stock kernel for sure. But I've been having to run my battery faster by using my workaround to avoid the music crackling.
JT's Super Clean ROM using TouchWiz
Just suggestions so we can all get on the same page and enjoy these badass mods.
P.S. What ROM are you using during testing of this kernel? I'll gladly switch to fix the issues

Phone random reboot. Troubleshooting help request.

The past two days my phone has been randomly rebooting. It has happened twice in two days. I have no idea how to pull any information from my phone to possibly see what is happening. I am moderatly tech savvy so with good directions I can do just about anything. If anyone is willing to help that would be great.
Phone: At&t GSII (obviously)
Rom: Cognition beta-4
Kernel: Entropy's doom v2
I am using set CPU with profiles. Not over clocking or undervolting, I just use it to underclock when phone gets to hot or battery gets to low.
Anything else you need to know or want me to do please let me know. Thanks.
Sent from my SAMSUNG-SGH-I777 using xda premium
Emil9727 said:
The past two days my phone has been randomly rebooting. It has happened twice in two days. I have no idea how to pull any information from my phone to possibly see what is happening. I am moderatly tech savvy so with good directions I can do just about anything. If anyone is willing to help that would be great.
Phone: At&t GSII (obviously)
Rom: Cognition beta-4
Kernel: Entropy's doom v2
I am using set CPU with profiles. Not over clocking or undervolting, I just use it to underclock when phone gets to hot or battery gets to low.
Anything else you need to know or want me to do please let me know. Thanks.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Complete reboot back to Samsung screen? Or back to bootanimation?
If all the way back to the Samsung screen, there isn't much you an do right now other than wait - I'll be putting an update out tonight, and one of the main features is that I finally got ramconsole working. Ramconsole is how /proc/last_kmsg (the last things a kernel printed before a reboot or crash) is implemented. Once I release my next kernel, if you flash it and another reboot back to the Samsung screen happens, the following will give valuable debug information if executed from Android Terminal Emulator or a similar app:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Then zip up last_kmsg.txt and post it - but as I said, you'll need to wait for the next kernel release before you can do this.
I haven't seen it reboot but it asks what launcher to use (because I didn't set a default) and the battery useage is reset. It will say it has been unplugged for 20 min while it has been for a few hours. Those factors make me think it does a full reboot.
Don't know if that helps. If there is anything else let me know aside from that I will flash the new kernel when its out. Thanks for all the great work
Sent from my SAMSUNG-SGH-I777 using xda premium
RE: Random Rebooting
Emil9727 said:
The past two days my phone has been randomly rebooting. It has happened twice in two days. I have no idea how to pull any information from my phone to possibly see what is happening. I am moderatly tech savvy so with good directions I can do just about anything. If anyone is willing to help that would be great.
Phone: At&t GSII (obviously)
Rom: Cognition beta-4
Kernel: Entropy's doom v2
I am using set CPU with profiles. Not over clocking or undervolting, I just use it to underclock when phone gets to hot or battery gets to low.
Anything else you need to know or want me to do please let me know. Thanks.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Very simple fix:
Uninstall SetCPU and reboot the phone and magically it will
no longer randomly reboot.
(you can always re-install it if you don't mind random reboots )
Good Luck!
You think it's set CPU even though I'm not over clocking?
Sent from my SAMSUNG-SGH-I777 using xda premium
SetCPU
Emil9727 said:
You think it's set CPU even though I'm not over clocking?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
How long do you actually think that it takes to simply uninstall
and reboot your phone to see for yourself?
Even if you don't over-clock whatever you do with it can cause
the rebooting problem you are describing.
I certainly am not going to test it for you since I never over-clock
or under-clock anything including my phone and computer.
If the phone was meant to run a lot faster or slower than the
the manufacturers would be advertising the phones with faster
specifications so they can sell more of them.
It's only makes good advertising sense.
Think of it this way, lets say you buy a new car and decided to put
jet fuel into the gas tank to make it have more horsepower so it can
run lot faster than it was designed for, do you think doing this will
make the car more or less reliable in the short or long term?
Misterjunky said:
Very simple fix:
Uninstall SetCPU and reboot the phone and magically it will
no longer randomly reboot.
(you can always re-install it if you don't mind random reboots )
Good Luck!
Click to expand...
Click to collapse
You claim SetCPU is the problem, where is your evidence?
I test my kernels using SetCPU, I have never had a problem.
I keep hearing anecdotes about SetCPU causing problems for people, but there is no way it can possibly cause stability issues. sysfs is sysfs, and that's that.
The only place where SetCPU might cause a problem is with screen-off profiles less than 800 MHz on kernels that don't have the SoD patch.
To the OP - Sorry I didn't release tonight, I got caught up in trying to help someone track down a power management issue with wifi. I'll do it when I wake up.
I am not stupid and the reason I was questioning was because I have OC/UC/UV before and I know what the stability issues are like with them. It is not something that happens frequently so it is hard to test. I have been going now for over 24 hours and no reboot. No changes to set CPU either. Primarily though I wanted a concise way to pull info so I can help people like entropy.
(Off topic a little) Manufactures might UC hardware for a few reasons. Battery capacity and heat are usually two of the big ones. If you stuck your phone in the freezer you could probably OC this phone to 2ghz and run stable. I OC to 1600 for fun and its completely stable. I clock it down if I'm out and it is hot or I am in the sun.
To entropy: its cool I check the forums every hour if not more frequently LOL. I think it has become an addiction. Once the kernel is out let me know what I can do to help.
*Cog + doom = cheat codes*
Sent from my SAMSUNG-SGH-I777 using xda premium
Flash the latest 10/16 releases and if you have another reboot you should be able to pull a /proc/last_kmsg
Entropy512 said:
Flash the latest 10/16 releases and if you have another reboot you should be able to pull a /proc/last_kmsg
Click to expand...
Click to collapse
Will do
Does this new release have OC/UC support?
Emil9727 said:
Will do
Does this new release have OC/UC support?
Click to expand...
Click to collapse
Same as the previous releases, which do.

[Q] Safe undervolting values

Hey guys, anyone have a good idea of what some safe undervolting values would be? I was just going to play around with them and not set it on reboot so I could just pull the battery, but I am unsure of how irreversible the damage could possibly be, if any.
I am running: Senseless 1.0
dsb's kernel
I actually have it underclocked slightly because I don't play games, and when I do they are something like Angry Birds, or Words when I am bored.
Bump, out of all of you who have undervolted none of you know any good values?
AtLemacks said:
Bump, out of all of you who have undervolted none of you know any good values?
Click to expand...
Click to collapse
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
WasabiWa83 said:
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
Click to expand...
Click to collapse
Cool, I didn't know what was "too much". How much better battery life did you see from -50?
Evo4gLI said:
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
Click to expand...
Click to collapse
Which Kernel are you running?
At -50mV across all frequencies, it reeeally varies. I never have a "normal" day with this phone. But, the shortest I've had using Ziggy's kernel from 192-1836gHz with on demand governor is around 7 hours. That was pretty heavy usage for me. Some games like Dead Space and Captain America, tons of internet, Pulse, texting, a few phone calls, music, and a little Netflix at night. The longest I've had has been 20+ hours. That's with very little gaming, a little internet, and mostly just texting. Stock battery, bump charged.
I'm really afraid to go too low, though. One time I was just seeing what would happen if I kept lowering it across all of the frequencies and it froze, then crashed. Had to battery pull to get it to work again.
I run DSB Kernel with SmartAssV2 underclocked to 1296, and before undervolting on my OEM battery I got 13 hours with a little over normal usage. Screen was on for about 2 hours total. On my extended battery I got like 27 1/2 hours, but obviously some of that time was overnight.
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
AtLemacks said:
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
Click to expand...
Click to collapse
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
nosympathy said:
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just -50, but I updated the kernel and forgot to remove the PH98IMG prior so I set the phone into bootloops. Had to factory reset(after trying everything else) and start over from backups.
Evo4gLI said:
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
Click to expand...
Click to collapse
See, I don't get the overclocking hype. It isn't hard to overclock when needed, so I feel underclocking is the better choice for battery life. The phone is fast as hell no matter what.
I may try to do some undervolting...but I am running clean rom 1.3 and dsb's smartass kernel, and I have been getting good battery life for what I use my phone for. I do have it overclocked though (on demand).
You won't damage the phone with undervolting. I mean a lockup might be a pain, but it won't damage the phone. Overvolting on the other hand could ruin the phone.
I will probably just stick with -50 across the board for now, I am tempted to pay for the full version just so I can save profiles and not have to set on boot.
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Running -75 on everything with incredikernel
bendirkss said:
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Click to expand...
Click to collapse
You sir must be using a Gnex. LOL

[Q] lulzactive cpu problem

I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2

Random freezes on ICS

I have recently just hopped back onto ICS AGAIN. I have used ICS ever since its been out for my region and every single try i will revert due to the same issue. Either battery life or random freezes.
This time i am really lost hope. I was hoping samsung could release something that worked for me but it never came. I have to seek help from all the pros
The situation:
I have flashed afew ICS ROMs and kernel combo. I tried
DXLP9 w/ stock, siyah, NEAK
DXLPB w/ stock, siyah, NEAK
Sensation ROM 3.5 with siyah.
They all had the same issue whether i UV them or not. I tried factory resets, clear cache, kernel cleaning scripts, even SD format.
They all will have random freezes on load. Its random so sometimes i cant recreate the situation. Most common ones are updating or downloading from market, when its near or starts to install. But i can watch videos and everything fine. GMaps sometimes freezes it too.
As for governer i use smartassv2 for siyah and lulzactive for NEAK and SIO as scheduler. Did try ondemand on stock and sometimes noop and NEAK. Same responses.
I ran sensation rom fine ytd with 1 widget and downloaded whatsapp and extweaks and UV and everything was stable. Watched pps the whole night. Totally fine and this morning i wanted to load my normal apps from market and it started to freeze on me.
Im really lost someone pls help me. If not i really have to go back to GB again.
Sent from my GT-I9100 using xda app-developers app
sianzb0i said:
I have recently just hopped back onto ICS AGAIN. I have used ICS ever since its been out for my region and every single try i will revert due to the same issue. Either battery life or random freezes.
This time i am really lost hope. I was hoping samsung could release something that worked for me but it never came. I have to seek help from all the pros
The situation:
I have flashed afew ICS ROMs and kernel combo. I tried
DXLP9 w/ stock, siyah, NEAK
DXLPB w/ stock, siyah, NEAK
Sensation ROM 3.5 with siyah.
They all had the same issue whether i UV them or not. I tried factory resets, clear cache, kernel cleaning scripts, even SD format.
They all will have random freezes on load. Its random so sometimes i cant recreate the situation. Most common ones are updating or downloading from market, when its near or starts to install. But i can watch videos and everything fine. GMaps sometimes freezes it too.
As for governer i use smartassv2 for siyah and lulzactive for NEAK and SIO as scheduler. Did try ondemand on stock and sometimes noop and NEAK. Same responses.
I ran sensation rom fine ytd with 1 widget and downloaded whatsapp and extweaks and UV and everything was stable. Watched pps the whole night. Totally fine and this morning i wanted to load my normal apps from market and it started to freeze on me.
Im really lost someone pls help me. If not i really have to go back to GB again.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
try with less UV, and more bus freq
pelpa87 said:
try with less UV, and more bus freq
Click to expand...
Click to collapse
but i even tried no UV and with stock. ytd i tried no UV again. seems to be performing well but i cannot let my phone run without UV cos it will drain battery very fast
Btw im using the same 5 cpu states but i turned off the 1.2GHz state. So its 200 to 1000. What do you mean more bus freq? Up cpu speed?
sianzb0i said:
but i even tried no UV and with stock. ytd i tried no UV again. seems to be performing well but i cannot let my phone run without UV cos it will drain battery very fast
Btw im using the same 5 cpu states but i turned off the 1.2GHz state. So its 200 to 1000. What do you mean more bus freq? Up cpu speed?
Click to expand...
Click to collapse
dunno about siyah, i use fluxi, u can ov bus. I think in siyah too.
The thing is simple, not every phone reacts equal. My phone for example doesn't handle strongs uv. I have to slightly uv it. Same as bus.
I even saw some phones that couldn't handle aokp without over volting. Ir getting higher bus.
In the other hand, uv is overrated. It doesnt saves as battery as everyone thinks. The screen is battety's worst enemy
Sent from my GT-I9100 using xda premium

Categories

Resources