Develop Bugs

i9000 goes off

Hi,
i have an Italian version of i9000 with jf5 firmware.
I have upgraded whit samsung kies my firmware.
now i have
pda xwjm3
phone xxjm2
csc itvjm1
now sometime my phone goes off
anyone have the same problem?
i read that this is a bug......

You read its a bug? Of course it's a bug.
It's either a bug with the firmware or with an application. I had the same problem when using SetCPU.
Sent from my GT-I9000

i have setcpu me too.
so the problem is this app?
just uninstall it?

I experienced it (no response completely unless I reinsert the battery) when with lag fix and GPS on, regardless eclair or froyo ROM.
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
I have a feeling that the problem was due to GPS or due to the 0513 pit, but I'm not sure - so far it's been okay so I bother not to break it for tests.

SetCPU shuts my device down... out of nothing...
i uninstalled setcpu and never happened again

mystaka said:
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
Click to expand...
Click to collapse
Slightly off-topic but... That'd actually be an overclock if I'm reading those numbers correctly. The default frequency is 1000/100mhz with a conservative setting, meaning it'll try to be as low as possible more or less. What you've done is set min-frequency to 400mhz, which in my book is an overclock from the stock 100mhz.
Back to semi on topic... SetCPU is known to cause problems on Galaxy S, and likely other devices aswell. Most problems has been more specifically caused by using ondemand setting when setting up profiles - for some reason the phone doesn't handle this setting well when it wakes from sleep.
I'm pretty sure I managed to get it working more or less flawlessly with an screen off profile at 400/100 with Conservative setting, though I reflashed shortly after those settings so never got to test it properly. Regardless, they might work if you want to mess about with it.

I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.

gettons said:
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
Click to expand...
Click to collapse
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100

insty said:
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
Click to expand...
Click to collapse
Great!This work
Thank you

I don't use setcpu but I have this problem in my two SGS. Using m5 and m6..

[Q] SetCPU Superuser Permissions

So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?

cmccollough said:
So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
Click to expand...
Click to collapse
From my understanding, you only set it once. i had set a widget because i thought set cpu had to be running. But i deleted it because if you think about it....superuser app already has the permissions set, and when you open setcpu it shows the current speed.....if it wasnt working it would show 800mhz then KICK into 1 ghz?....thats what i think. You shouldnt need to worry.

Great, thanks for the response.
Sent from my HTC Vision using XDA App

same here. from time to time this popup comes.
anyway i cannot see any benefit from running setcpu as the profiles are not working for me.
i tried setting up screen off profile. this never triggers.
i leave setcpu deinstalled now. battery life is good so far

snudel said:
i tried setting up screen off profile. this never triggers.
Click to expand...
Click to collapse
How can you tell if it triggers or not?

cmccollough said:
How can you tell if it triggers or not?
Click to expand...
Click to collapse
Good question. Can't find anything in logcat.

set notifications.
on the magic you could see him switching profiles right after turning on the screen
you wont see it on the g2

I agree, something is fishy with this. EVERY time I open setcpu it gives me the su permissions granted window like its not being saved in memory
Sent from my HTC Vision using XDA App
EDIT: After shopping around on the market I came across an app called "CPU Tuner". The UI is nice and has roughly the same customization as setcpu if not more. It does take a bit of getting used too but i'm more than willing since the profile notification actually cycles with this app vs. setcpu. I'll give it a shakedown tomorrow as it's getting too late here to test.

cpu tuner doesn't work for me.
in profiles, it just shows 700mhz to 800mhz, which makes it useless as i want to underclock to 200 when screen is off.

That toast pop-up is nothing to worry about, its just something that has featured in the last couple of SU builds, it doesn't mean your app is not working.
I just turn the notification off in the SU settings.

I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App

cmccollough said:
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.

jark99 said:
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Running the setcpu widget on my phone caused instability issues at higher clocks (feeling ballzy w/ flippy's 1.8 kernel). After removing the widget my profiles were hit and miss for some reason.
As far as the battery issue goes, anyone running CM RC2 and earlier might want to check out nightly 36, apparently there was a memory leak causing battery drainage ( I don't know anything about what it means but common sense leads me to believe a leak is bad lol). If anyone is still not satisfied with setcpu I highly recommend CPU tuner.

jark99 said:
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Yes I have the widget on my homescreen. Weird that so many people get different results

Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?

cmccollough said:
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
Click to expand...
Click to collapse
http://www.droidforums.net/forum/rescue-squad-guides/47871-overclocking-101-a.html
Centered around the OG Droid but basic concepts still stand.
- Just picked up an app called SuperPower, had it a while back and had issues..but it's been update a lot since then. Looks like it's an all purpose battery management app that has the ability to govern cpu speed also. I'll test drive it and see how it works.

My battery life has improved markedly since installing CM nightly #36 and Pershoot's latest kernel. I've been using my phone pretty heavily over the last 8hours and still have over 50% left. Lots of texts, emails and websurfing etc.

Screen on screen off problem Vision rom

I just flashed the vision rom on g2 about 6 hours ago earlier today from Rom Manager and its running great except that when the phone goes into screen off mode, and then i try to turn the phone back screen on the screen stays black but the bottom 4 buttons still glow, and when i click stuff on the screen it clicks them but its black and there is NO brightness at all NO LIGHT lol, now this isn't the phones problem because on the normal froyo backup i have it works fine, but i am in love with sense, except it really pisses me off that it does this, if anyone can help it would be great or if someone has experienced this issue and found any way to solve it, please let me know how. If you want a video let me know i can make one.

TheRealEvo said:
I just flashed the vision rom on g2 about 6 hours ago earlier today from Rom Manager and its running great except that when the phone goes into screen off mode, and then i try to turn the phone back screen on the screen stays black but the bottom 4 buttons still glow, and when i click stuff on the screen it clicks them but its black and there is NO brightness at all NO LIGHT lol, now this isn't the phones problem because on the normal froyo backup i have it works fine, but i am in love with sense, except it really pisses me off that it does this, if anyone can help it would be great or if someone has experienced this issue and found any way to solve it, please let me know how. If you want a video let me know i can make one.
Click to expand...
Click to collapse
You have overclocked right?
this is a very common problem
what you need to do is set up a screen of profile on setcpu
min:245
max:368
scaling : powersave
and make sure you tick Enable on profiles menu
this should solve your problem.

bahmanxda said:
You have overclocked right?
this is a very common problem
what you need to do is set up a screen of profile on setcpu
min:245
max:368
scaling : powersave
and make sure you tick Enable on profiles menu
this should solve your problem.
Click to expand...
Click to collapse
Thank you for the information, just set everything up the way you said to and gonna give it a test now, thank you!!
Edit: also, i have it clocked at 1420 max and 800 min, and a set profile for the one that you gave me and one so if it overheats to clock itself down, should i keep the min to 800 or should i make it lower, this is for when the phone is on, when it goes screen off it goes into the profile you gave me, thanks.

TheRealEvo said:
Thank you for the information, just set everything up the way you said to and gonna give it a test now, thank you!!
Edit: also, i have it clocked at 1420 max and 800 min, and a set profile for the one that you gave me and one so if it overheats to clock itself down, should i keep the min to 800 or should i make it lower, this is for when the phone is on, when it goes screen off it goes into the profile you gave me, thanks.
Click to expand...
Click to collapse
why do you have your min at 800 mhz anyway?
there is no need for that put the min at 245 your phone will scale up when it needs
to. and for scalling, ondemand works for me best ,you can can try different ones to see which on gives you better performance and battery life. dont use performance scaling for everyday use though .

proper way to use smartass?

i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)

Sorry. This should be in Q&A.....
Sent from my OMFGB powered hTc Incredible.

watt9493 said:
i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)
Click to expand...
Click to collapse
I ran OMFGB 1.1.1 for a long time before they screwed up 1.2(soooooo many errors), and really felt the need to have a lockscreen music controler(1.1.1 doesn't). I always ran 128/768, on 1.1.1 it should run perfect(I run chad's kernel though), just unlock slowly. If you want a faster unlock set it 245/768. Either one of those will get you really good battery life(128 being better obviously). If you are running 1.2, I highly recommend you set it atleast at 921(i think) or above as that just doesn't run as smooth. Also note the way smartass works, unless you want to kill battery life everytime you turn the screen on, try to set the max the lowest possible as it will sit as a frequency the phone feels it should run at without losing any speed(most of the time it's 1036 if you've overclocked). So unless you are just texting or calling, it's not bad, but any multitasking or big app using when the screen on, it'll jump way up.
I believe Chad is working on an ingenious kernel that tries to scale intelligently to what it is doing at all times so it'll save battery life not only when the screen is off, but also while the screen is on.

Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.

watt9493 said:
Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.
Click to expand...
Click to collapse
Oh, well, there is no point for a screen off one if you are using smartass on all your profiles. When it's not doing anything, it automatically scales down to the lowest setting possible(128 for best battery but slow unlock speeds or double clicks sometimes, 245 fixes those problems but using a fraction more battery).
I have a Normal profile(128/768), a Temp profile(245/614), just make sure if you are using GPS you manually scale it up some, my phone always ran like crap when Navigating anything less then 883, but everything, and I mean everything usually was fine at 768 on 1.1.1. If you are running 1.2 probably want to do 883 then 998 for GPS.

[Q] display problem when UV

im using ncx 099a kernel and since i flash these kernel, the screen sometimes flicker like hell......this is happen when im palying game and then it continue to shake the display...when im trying a force reboot to bootloader, the screen died only vibrate...but when im push longer it go to bootloader mode ok...try to restore nandroid but still the same..
and some other times, there are strange pixel color showing up....
i try to fix this by OV my phone a little...and now everythings fine...
my question is, is UV or maybe any other setting to kernel or rom will have this massive effect on our phone...

No
No not until u underclock it to extreme levels.

aman360elite said:
No not until u underclock it to extreme levels.
Click to expand...
Click to collapse
underclock...mine is lowest to 51mhz max to 1300mhz....this is the setting from the kernel
undervolt...i think not that extreme...i have been using the same setting even when in my evo 3d...just -50mv from original mv..