Page 21 of 36 FirstFirst ... 11161718192021222324252631 ... LastLast
Results 401 to 420 of 703
  1. wprater's Avatar
    Posts
    240 Posts
    Global Posts
    251 Global Posts
    #401  
    Quote Originally Posted by VitViper View Post
    Just noticed something...
    My phone LCD off and NO cards open, LunaSysMgr was using 80% CPU for some reason. Restarted LunaSysMgr... now Java is using 95%. Rebooting the phone. Something is fubar'd with Java/Luna. This might explain crappy battery life.... Will look into it further.
    Im getting the same issues now with the Java cpu utilization with the screen off.. any updates on this?
  2. #402  
    I'm having issues with the clock speeding up time slowly. Like in 6 hours the time will be fast 10 min. Also having an issue where using MyTether for an extended period of time causes no texts/voicemails to come through until after a restart. Both of these issues are fixed after a restart, but considering how long it takes for this device to perform that task it is rather irritating. Anyone else had these issues??
  3. #403  
    Dirtygreek,

    I've always had the understanding that EVDO is not used when wifi is active. So if you're using wifi to check, you won't see it with iwconfig
  4. #404  
    I am currently getting lock-up's on my Pre whenever I have it on the Touchstone. It will happen idle or if I'm connected through WinSCP. I've tried both:

    exec /opt/sbin/cpuspeed -i 1 -M 600000 -r -p 15 75
    exec /opt/sbin/cpuspeed -i 2 -M 600000 -r -p 55 75

    with similar results.
    I'm going to start with just the original CPU scaling options to see if that has any effect.


    If I helped you or you have downloaded one of my files,
    then least you could do is click the "Thanks" button.
  5. #405  
    Quote Originally Posted by Abyssul View Post
    I am currently getting lock-up's on my Pre whenever I have it on the Touchstone. It will happen idle or if I'm connected through WinSCP. I've tried both:

    exec /opt/sbin/cpuspeed -i 1 -M 600000 -r -p 15 75
    exec /opt/sbin/cpuspeed -i 2 -M 600000 -r -p 55 75

    with similar results.
    I'm going to start with just the original CPU scaling options to see if that has any effect.
    perhaps you could try the screen monitoring options. so that it doesn't scale when the screen is on. Although, I know your problems stem from mostly when the screen isn't on. so, you could also try two speeds, 250000 when the screen is off and 600000 or 550000 when the screen is on.
  6. #406  
    For some reason when I turn on CPU scaling (whether max speed is clocked to 500 or 600) my proximity sensor doesn't work. I end up turning on airplane mode, calling people, and doing all kinds of stuff with the phone against my face. The sensor works fine with CPU scaling off. This is the only issue. Any ideas?
  7. VitViper's Avatar
    Posts
    83 Posts
    Global Posts
    102 Global Posts
    #407  
    Quote Originally Posted by wprater View Post
    Im getting the same issues now with the Java cpu utilization with the screen off.. any updates on this?
    It only happens when I SSH in via an EVDO connection. Which makes me believe that EVDO is possibly handled via a Java service thread....
  8. #408  
    Im kinda new to cpu scaling so bear with me please.

    This is what my time in state shows:
    root@castle:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    600000 411
    550000 1178
    500000 33774
    250000 783
    125000 39484
    root@castle:/#

    When I try to enter this string:

    exec /opt/sbin/cpuspeed -i 2 -M 600000 -r -p 55 75

    Nothing happens, The cursor drops down 1 line a just sits there.




    root@castle:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    600000 411
    550000 1178
    500000 33774
    250000 783
    125000 39484
    root@castle:/#
    root@castle:/# exec /opt/sbin/cpuspeed -i 2 -M 600000 -r -p 55 75














    Am I doing something wrong?
  9. #409  
    Quote Originally Posted by dsjr2006 View Post
    I'm having issues with the clock speeding up time slowly. Like in 6 hours the time will be fast 10 min. Also having an issue where using MyTether for an extended period of time causes no texts/voicemails to come through until after a restart. Both of these issues are fixed after a restart, but considering how long it takes for this device to perform that task it is rather irritating. Anyone else had these issues??
    Same here, although it's somewhat less severe. FWIW, people are having this problem with stock Pres as well. Pretty unbelievable that Palm can't nail down, you know, the time.
  10. #410  
    Quote Originally Posted by 2sslow View Post
    Im kinda new to cpu scaling so bear with me please.

    This is what my time in state shows:
    root@castle:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    600000 411
    550000 1178
    500000 33774
    250000 783
    125000 39484
    root@castle:/#

    When I try to enter this string:

    exec /opt/sbin/cpuspeed -i 2 -M 600000 -r -p 55 75

    Nothing happens, The cursor drops down 1 line a just sits there.




    root@castle:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    600000 411
    550000 1178
    500000 33774
    250000 783
    125000 39484
    root@castle:/#
    root@castle:/# exec /opt/sbin/cpuspeed -i 2 -M 600000 -r -p 55 75














    Am I doing something wrong?
    You are suppose to edit the cet-cpuspeed file.

    "vi /etc/event.d/cet-cpuspeed"

    Then scroll down to the exec line and replace it. Make sure you are in insert mode by type "I" first. When you are done, press escape and then ":wq" to save and quit your progress.


    If I helped you or you have downloaded one of my files,
    then least you could do is click the "Thanks" button.
  11. #411  
    Quote Originally Posted by catalystmediastudios View Post
    For some reason when I turn on CPU scaling (whether max speed is clocked to 500 or 600) my proximity sensor doesn't work. I end up turning on airplane mode, calling people, and doing all kinds of stuff with the phone against my face. The sensor works fine with CPU scaling off. This is the only issue. Any ideas?
    hey, if the speakerphone is in use the proximity sensor won't turn the screen off. You using that maybe?
  12. #412  
    with...
    Code:
    exec /opt/sbin/cpuspeed -m 250000 -M 600000 -a /sys/devices/platform/lcd.0/panel_state -A 10 -r -i 10
    I get true scalling range from 250000 - 600000.

    varies with what i am doing but works well. but is not super stabell video flickers a bit did not bother to test pandora i am going back to the settings in the OP i liked those very stable except i will be over clocking to 600000



    in_state
    600000 17610
    550000 7626
    500000 7806
    250000 29118
    125000 0
    in_state
    600000 17610
    550000 7626
    500000 7806
    250000 29145
    125000 0
    in_state
    600000 17610
    550000 7626
    500000 7806
    250000 29166
    125000 0
    in_state
    600000 17610
    550000 7626
    500000 7806
    250000 29186
    125000 0
    in_state
    600000 17629
    550000 7627
    500000 7807
    250000 29191
    125000 0
    MatterOfFactJack
  13. #413  
    I tend to max the speed with the screen on but I might try not maxing so that I can run stuff like the clock apps without worrying that I'm going to screw up the phone by having the screen on all night. I suppose it isn't a good habit anyways.

    I am running max 600 min 125, the -p is 15 75. monitoring the screen to lock max when screen is on and full scaling when off.
    I'd paste it but not sure if I can even copy using the terminal app, and I'm on the Pre. Haven't seen any problems at all with this setup. During my normal usage it spends about 75% of the time at 125000 and 20% at 600000.

    I never got a grasp on the -p parameters, how do they affect responsiveness? I just blindly try different ones.
  14. #414  
    Just wanted to say that, after installing webOS 1.2 from the webOS doctor that was leaked, this cpu scaling implementation(the cet one) causes it to freeze as soon as Luna comes up. Could be possible something changed that the cet scaling uses, I dunno, hopefully this can be resolved.
  15. #415  
    So my cpu scalling at 600000-250000 has killed my battery half in hald and I been having phone closed all day in my pocket will try it with 500000 next see how it goes.

    Quote Originally Posted by Elysian893 View Post
    Just wanted to say that, after installing webOS 1.2 from the webOS doctor that was leaked, this cpu scaling implementation(the cet one) causes it to freeze as soon as Luna comes up. Could be possible something changed that the cet scaling uses, I dunno, hopefully this can be resolved.
    When was 1.2 leaked and how can I get it? If you can please PM what it does or a link to all that info i' d appreciate it. I am on pre now no computer otherwise I'd do th research. Thanks ahead of time.
    MatterOfFactJack
  16. #416  
    Quote Originally Posted by hmagoo View Post
    I tend to max the speed with the screen on but I might try not maxing so that I can run stuff like the clock apps without worrying that I'm going to screw up the phone by having the screen on all night. I suppose it isn't a good habit anyways.

    I am running max 600 min 125, the -p is 15 75. monitoring the screen to lock max when screen is on and full scaling when off.
    I'd paste it but not sure if I can even copy using the terminal app, and I'm on the Pre. Haven't seen any problems at all with this setup. During my normal usage it spends about 75% of the time at 125000 and 20% at 600000.

    I never got a grasp on the -p parameters, how do they affect responsiveness? I just blindly try different ones.
    Please post your settings. I would like to try them out.


    If I helped you or you have downloaded one of my files,
    then least you could do is click the "Thanks" button.
  17. #417  
    Quote Originally Posted by jack87 View Post
    So my cpu scalling at 600000-250000 has killed my battery half in hald and I been having phone closed all day in my pocket will try it with 500000 next see how it goes.



    When was 1.2 leaked and how can I get it? If you can please PM what it does or a link to all that info i' d appreciate it. I am on pre now no computer otherwise I'd do th research. Thanks ahead of time.
    http://forums.precentral.net/palm-pr...ready-out.html

    Theres a megaupload download link here:

    MEGAUPLOAD - The leading online storage and file delivery service

    You must disable the UpdateDaemon to do this(chmod -x UpdateDaemon, then killall UpdateDaemon, think the UpdateDaemon is in /usr/bin/, but I could be wrong off the top of my head). Right now the only way to install it is via the webOS Doctor image there, so you're gonna lose everything.

    I also started a list of the changes here:

    http://forums.precentral.net/palm-pr...tionality.html
  18. #418  
    Quote Originally Posted by Abyssul View Post
    Please post your settings. I would like to try them out.
    Code:
    exec /opt/sbin/cpuspeed -i 5 -p 15 75 -M 600000 -a /sys/devices/platform/lcd.0/panel_state -A 10 -D -C -r
    max speed 600000 (-M 600000)
    adjust scaling twice a second (-i 5)
    check screen state once per second (-A 10)
    do not force minumum speed while screen is turned off (-D)
    run at maximum speed while screen is turned on (-C )
    restore previous CPU speed on exit (-r)
  19. as4life's Avatar
    Posts
    577 Posts
    Global Posts
    733 Global Posts
    #419  
    Quote Originally Posted by Elysian893 View Post
    Just wanted to say that, after installing webOS 1.2 from the webOS doctor that was leaked, this cpu scaling implementation(the cet one) causes it to freeze as soon as Luna comes up. Could be possible something changed that the cet scaling uses, I dunno, hopefully this can be resolved.
    How is battery life running on 1.2 stock?
  20. #420  
    okay so today i ran the default settings the files are set to and my bettery suffered. only got 5.5hours.

    i am a little ignorant to this but if someone could post some quick commands to removing it and setting everything back to default so i can compare battery life again just incase something else might be draining the juice.
    MatterOfFactJack

Posting Permissions