[Q] Reboot when using GPS and screen off - Wildfire Q&A, Help & Troubleshooting

Hi,
I'm running a cyanogenmod 7 nightly from 19 July (but had the same problem with all previous cyanogenmod 7 nightlies as well) on my Wildfire.
GPS always works and worked fine, only when using an app that requires the GPS (navigon, openbmap, google map, google navigations, google tracks....) and I let the screen power-off ==> the phone will reboot afer a random amount of time.
I do run all the programmes of my SD since my internal memory doesn't have enough free space.
This only happens when I'm using the GPS and letting the phone power it's screen off.
My kernel settings are: ONDEMAND min 352, max 729
I'm guessing it might work if I use a higher minimum value or set the kernel to "performance", but shouldn't it automatically work with "ondemand'?
Haven't read anyone else with similar problems and found that a bit weird.

I just test it with cpu min frequency also at 729 and it still rebooted
nobody has any clue?

Zorkman said:
I just test it with cpu min frequency also at 729 and it still rebooted
nobody has any clue?
Click to expand...
Click to collapse
Try not using such a high frequency on your cpu as it is not stable for all try like 652 for a while and definatly dont use the lowest frequency for your low setting.
Sent from my GT-P1000 using XDA Premium App

-Howard- said:
Try not using such a high frequency on your cpu as it is not stable for all try like 652 for a while and definatly dont use the lowest frequency for your low setting.
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
Hmm... I don't really think that is the problem because when I look at my CPUSpy readings i have:
729 MHz : 3:32:51
480 MHz: 1:59:44
352 MHz: 0:36:58
Deep Sleep: 37:38:39
and I've seen occasions where it had run @ 729MHz for more than ten hours...
still screen off + GPS can kill it always in less than 30min

Related

Setcpu troubleshooting

I have setcpu running on desire with neophyte v1.2 ROM. It was running perfectly until I put it to charge overnight while sleeping.. when I woke up, the display shows that the phone is running at max speed constantly when it was set to "ondemand". I also have a profile with 245 min/max when screen off but when I wake up after 8hrs, I go to the info tab, I see that my phone is spending more time on max speed than 245 which doesn't make sense because the phone has majority of time with screen off..
What am doing wrongly here?
Sent from my HTC Desire using XDA App
webber2109 said:
I have setcpu running on desire with neophyte v1.2 ROM. It was running perfectly until I put it to charge overnight while sleeping.. when I woke up, the display shows that the phone is running at max speed constantly when it was set to "ondemand". I also have a profile with 245 min/max when screen off but when I wake up after 8hrs, I go to the info tab, I see that my phone is spending more time on max speed than 245 which doesn't make sense because the phone has majority of time with screen off..
What am doing wrongly here?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
need help....
what other profiles do you have?
i have 2 profiles.
one is 245 min 245 max when screen off (priority 100)
the other is 245 min 998 max when charging or full when charging (priority 50)
did i do anything wrong?
Has ur SetCPU got granted by SuperUser?
lpachuong said:
Has ur SetCPU got granted by SuperUser?
Click to expand...
Click to collapse
yup it is. in fact it was working properly until i leave it to charge. i tried uninstalling and re-installed but still it clocks at 998. the sleep profile doesnt seem to work well too
Try using a different ROM.
I experienced the same with the other ROMs when using the ondemand governor. I'm now using Nextsense 5.3 and the kernel allows "interactive" governor in SetCPU and my CPU speed stays at the lowest limits when idle.
amf said:
Try using a different ROM.
I experienced the same with the other ROMs when using the ondemand governor. I'm now using Nextsense 5.3 and the kernel allows "interactive" governor in SetCPU and my CPU speed stays at the lowest limits when idle.
Click to expand...
Click to collapse
do u have any profile for screen off? does it work?
from the info tab, i see my phone spent more time on max speed than min even though most of the time the screen is off
webber2109 said:
do u have any profile for screen off? does it work?
from the info tab, i see my phone spent more time on max speed than min even though most of the time the screen is off
Click to expand...
Click to collapse
Yup it works. Screen off profile--> Max=384 // Min=245
Try a ROM that supports interactive governor.
EDIT:
My "Time in State"
245 = 1352167
998400 = 18389

Proximity Sensor Problem w/ CM7?

I searched but couldnt find exactly what I'm looking for. When I press the power button or trackpad to wake the phone up in the dark, it wont turn on. Only the soft keys will light. Any advice?
If you have the CPU overclocked that could be the culprit. CM is notorious for not playing nice with any speeds over 1 GHz. Set is at 1017 or whatever is closest to that and it should be fine.
hiko36 said:
If you have the CPU overclocked that could be the culprit. CM is notorious for not playing nice with any speeds over 1 GHz. Set is at 1017 or whatever is closest to that and it should be fine.
Click to expand...
Click to collapse
I keep mine at 1.4 with no issues
Sent from my Vision using XDA Premium App
I don't see how this is an issue with the proximity sensor...
However, as per the above poster, CM has issues with overclocking. I experienced the same issue when I first installed CM7 and my options were to disable overclocking or disable the on/off animations (I chose the latter).
With CM7 I noticed the cpu is set @ a range of 245-1400. Use setcpu profile for screen off @ 245-368 and a regular profile 700-1017...you will have less diffulculty wakeing ur device. If you keep it @ the default settings it tries to jump to the highest frequency and uses nothing in between and creates a lag and sometimes even a soft reboot
Sent from my HTC Vision using XDA Premium App

[Q] [CPU] My CPU Speed automatically goes down to 810Mhz

My CPU Speed automatically goes down to 810Mhz on all overclocked kernels.
Even in CM10 kernels,
It happens in between while I play a game or so.
Even if I install Kernel with only GPU overclock, it still happens.
But never happens on stock kernels. I have to manually increase the CPU speed by setCPU.
Any Solutions for it Guys?
Moved to Q&A
Try to use Kernel tuner, and normally the device uses 810 mhz too cool down...
patato800 said:
Try to use Kernel tuner, and normally the device uses 810 mhz too cool down...
Click to expand...
Click to collapse
Used kernel tuner but still the same result, it goes to 810mhz even if the phone is not hot (just homescreen) and when i increase it, it remains at max even if i play games and make it hot. but after some time (say 15 or 20 minutes) even if I am in standby mode the cpu goes down to 810Mhz. previously at some point it was 1134Mhz.
Guys, anyone with some help. It has even started to occur in Complete stock ROM. (flashed the ftf on locked bootloader, still the max cpu spped drops from 1.5 Ghz to 810 Mhz, some times both cores)
halleyrokz said:
Guys, anyone with some help. It has even started to occur in Complete stock ROM. (flashed the ftf on locked bootloader, still the max cpu spped drops from 1.5 Ghz to 810 Mhz, some times both cores)
Click to expand...
Click to collapse
I had the same problem but i discoverd that the Battery saver pro causes that problem for me. If you use the seme app untick control CPU frequency.
It is actually a built in security feature of our phones which gets activated when temperature of phone goes high . At least that's what I know .
Sent from my Xperia S using xda premium
Here's solution!!!
http://forum.xda-developers.com/showthread.php?p=32245228
Send from my stupid lt26i

Delay in receiving a call

So when my phone screen is off, and I receive a call, the ringtone plays for about 3-4 seconds and then half way through the ringing, the screen turns on. I'm running ktoonsez kernel version 6/10
Do I need to increase a setting or something?
Have your off screen MHz too low I bet.
stevessvt said:
Have your off screen MHz too low I bet.
Click to expand...
Click to collapse
This is the first thing I thoguht of too.
Try setting it to 384 and see if it improves.
Skipjacks said:
This is the first thing I thoguht of too.
Try setting it to 384 and see if it improves.
Click to expand...
Click to collapse
stevessvt said:
Have your off screen MHz too low I bet.
Click to expand...
Click to collapse
My settings are :
MIN/MAX : 189 Mhz and 1890 Mhz
Screen Off Profile Mhz: 486 Mhz
Disable Screen Off Mhz Call: Enabled
Screen Off Profile Sched: noop
Screen Off GPU Max Mhz: 200
Which one's do i increase? and 384 isn't an option for me, it's either 378 or 189 (those are the lowest)
Change your min/max to 384(378?)/1890 and your screen off to 5XX, dont remember what that number is...
kevinrubio1 said:
My settings are :
MIN/MAX : 189 Mhz and 1890 Mhz
Screen Off Profile Mhz: 486 Mhz
Disable Screen Off Mhz Call: Enabled
Screen Off Profile Sched: noop
Screen Off GPU Max Mhz: 200
Which one's do i increase? and 384 isn't an option for me, it's either 378 or 189 (those are the lowest)
Click to expand...
Click to collapse
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
stevessvt said:
Change your min/max to 384(378?)/1890 and your screen off to 5XX, dont remember what that number is...
Click to expand...
Click to collapse
Okay I increased it to 378 Mhz and my screen off to 594 Mhz! I'll leave my phone to the side for a couple of minutes and see if it has the delay or not!
Skipjacks said:
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
Click to expand...
Click to collapse
Thanks, that makes perfect sense! I just set it to " Selected Scaling Max" because I couldn't find "No change" , is that the same?
kevinrubio1 said:
Thanks, that makes perfect sense! I just set it to " Selected Scaling Max" because I couldn't find "No change" , is that the same?
Click to expand...
Click to collapse
Yes. Same thing.
Skipjacks said:
Yes. Same thing.
Click to expand...
Click to collapse
It worked! Thanks skip
Sent from my SGH-M919 using xda app-developers app
Skipjacks said:
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
Click to expand...
Click to collapse
Great info! But partly incorrect.
Ktweaker is not like your other CPU tweaking apps. The app is not doing the screen on change. The kernel itself is doing that. If you look at the last_kmsg you will see the lines outputting the change. It also contains no screen on receiver which is needed for listening for screen events. Ktoonsez has kernel powers, they are better than APIs But yes, the max screen off CPU will cause lag when receiving a phone call for the reasons you state. It needs power to do its processes but is limited to the max CPU setting until the screen awakes.
But also increasing the min CPU levels helps too. I also think depending on which governor is used, that only one CPU is allowed to go on when the screen is off. Which is a great battery saver.
elesbb said:
Great info! But partly incorrect.
Ktweaker is not like your other CPU tweaking apps. The app is not doing the screen on change. The kernel itself is doing that. If you look at the last_kmsg you will see the lines outputting the change. It also contains no screen on receiver which is needed for listening for screen events. Ktoonsez has kernel powers, they are better than APIs But yes, the max screen off CPU will cause lag when receiving a phone call for the reasons you state. It needs power to do its processes but is limited to the max CPU setting until the screen awakes.
But also increasing the min CPU levels helps too. I also think depending on which governor is used, that only one CPU is allowed to go on when the screen is off. Which is a great battery saver.
Click to expand...
Click to collapse
wait so if I set the screen off mhz to 702, I would be fine and I would be saving battery?
kevinrubio1 said:
wait so if I set the screen off mhz to 702, I would be fine and I would be saving battery?
Click to expand...
Click to collapse
Yes you would save battery. And that should be high enough to let the processes carry out.
Sent from my SGH-M919 using Tapatalk 2
where is the screen setting menu??
i have the same problem how do i find the setting?

[Q] Idles at 1134 Mhz

Hi,
I have this Problem since I bough my phone last year. From time to time it gets into a state where it is just eating the battery. Only a reboot helps.
I have installed Kernel Tweaker now and see that in this problem state it runs at 1134 Mhz all the time.
What can I do?
Thanks,
Ropo
PS: CPU min frequency is set to 384000
ropoman said:
Hi,
I have this Problem since I bough my phone last year. From time to time it gets into a state where it is just eating the battery. Only a reboot helps.
I have installed Kernel Tweaker now and see that in this problem state it runs at 1134 Mhz all the time.
What can I do?
Thanks,
Ropo
PS: CPU min frequency is set to 384000
Click to expand...
Click to collapse
Change governor
Sent from my GT-I9195 using XDA Premium 4 mobile app
Aronuser said:
Change governor
Click to expand...
Click to collapse
I think I tried them all.
Now (don't have the problem now) when I use powersave it goes to 1134 Mhz, with ondemand 384 Mhz. I leave it on ondemand and check again the next time the problem occurs.
ropoman said:
I think I tried them all.
Now (don't have the problem now) when I use powersave it goes to 1134 Mhz, with ondemand 384 Mhz. I leave it on ondemand and check again the next time the problem occurs.
Click to expand...
Click to collapse
With On-demand and ROW I don't have the issue.

Categories

Resources