Page 24 of 56 FirstFirst ... 14192021222324252627282934 ... LastLast
Results 461 to 480 of 1118
  1. #461  
    Quote Originally Posted by rwhitby View Post
    Can't have it all *yet*

    As soon as we work out the way to prevent reboot loops which would require a visit to the webOS Doctor if your device didn't like the settings you chose, we'll implement that.

    But I expect Jason R or Casey@l337tech will probably soon have either an AUPT-4 binary patch or an update to CPU Scaler Ultimate to cover this as well, which is why we're focusing on the installation and upgrade scenarios first (leaving room for others with good technical solutions to participate in the ecosystem).

    -- Rod
    Understood! I wonder how hard it would be to implement a reboot counter into govnah? Similar theory to the resolution changes in Windows. If the resolution doesn't work and your screen goes black, it reverts after X seconds. Well if your phone doesn't boot properly after X tries, revert kernel settings.
    Last edited by sipple31; 05/06/2010 at 10:44 PM. Reason: typo. :-)
  2. #462  
    Thanks to the devs for all the hard work!
    I have a Sprint Pre running 1.4.1.1. and have installed UK and Govnah.
    I previously had the SPK and thought I should heed Rod's sage advice (as I always try to do) and go back and check to see if my LunaSysMgr and PmNetConfigManager were properly removed and back to the pristine files. (better late than never). I'm not having any issues other than the occasional screen pause / stutter, which may or may not even be associated to a kernel.
    Anyhow, after a lot of searching on how exactly I needed to check these files, I realized I could do this from the WOSQI Linux Command Line. So, I downloaded the latest version of that, and then downloaded the proper doctor file from the webos internals link into the same directory .
    Here's what I got:

    Code:
    root@palm-webos-device: grep LunaSysMgr /md5sums
      16b94adb47c798ee0c42d69e7304b29e *./usr/lib/libLunaSysMgrIpc.so
      dea90948f6841a85b0efa4c13d966267 *./usr/bin/LunaSysMgr
      0776cbcec54129acd4a41c617b581245 *./etc/event.d/LunaSysMgr
    root@palm-webos-device: md5sum /usr/bin/LunaSysMgr
      ca6a3981c382b01a559d7186742f1fe5  /usr/bin/LunaSysMgr
    root@palm-webos-device: grep PmNetConfigManager /md5sums
      1d5f655692a91f0c3bf274ade55b5d15 *./usr/bin/PmNetConfigManager
      2edc15faf767d2c251559c9626e5703a *./etc/event.d/PmNetConfigManager
    root@palm-webos-device: md5sum /etc/event.d/PmNetConfigManager
      2edc15faf767d2c251559c9626e5703a  /etc/event.d/PmNetConfigManager
    Can anyone tell me if what I have is correct, or should I doctor?
    Bear with me, but I think what I'm looking for is for the files to match, and it appears to me that the PmNetConfigManager files match, but the LunaSysMgr doesn't.
    I was following this same line of questions back on pages 21-22, but still unsure if I even did the check correctly. And my LunaSysMgr doesn't match what Rod has on his device from back on page 18.

    Thanks again for any advice,
    JB
  3. #463  
    Thanks Unixpsycho & Rod, this is superb.


    As you guys are obviously very clever I expect something similar has already been thought of, but One thing that occurred to me on the issues of overclocking, heat levels & life of CPU..

    Would it be possible for the overclocking to be set as it currently is, lets say using screen state and the 500/800Mhz setting. But also throttle the overclock if the temps start to get beyond a threshold? This would safeguard the life of the cpu from excessive heat.

    Many Thanks.
  4.    #464  
    Descaling based on temperature is on the roadmap, but my free development time is currently being spent on getting Preware 1.0 out the door so that orange+tap will work for kernel uninstall for everyone.

    -- Rod
  5.    #465  
    Quote Originally Posted by jkb2618 View Post
    Thanks to the devs for all the hard work!
    I have a Sprint Pre running 1.4.1.1. and have installed UK and Govnah.
    I previously had the SPK and thought I should heed Rod's sage advice (as I always try to do) and go back and check to see if my LunaSysMgr and PmNetConfigManager were properly removed and back to the pristine files. (better late than never). I'm not having any issues other than the occasional screen pause / stutter, which may or may not even be associated to a kernel.
    Anyhow, after a lot of searching on how exactly I needed to check these files, I realized I could do this from the WOSQI Linux Command Line. So, I downloaded the latest version of that, and then downloaded the proper doctor file from the webos internals link into the same directory .
    Here's what I got:

    Code:
    root@palm-webos-device: grep LunaSysMgr /md5sums
      16b94adb47c798ee0c42d69e7304b29e *./usr/lib/libLunaSysMgrIpc.so
      dea90948f6841a85b0efa4c13d966267 *./usr/bin/LunaSysMgr
      0776cbcec54129acd4a41c617b581245 *./etc/event.d/LunaSysMgr
    root@palm-webos-device: md5sum /usr/bin/LunaSysMgr
      ca6a3981c382b01a559d7186742f1fe5  /usr/bin/LunaSysMgr
    root@palm-webos-device: grep PmNetConfigManager /md5sums
      1d5f655692a91f0c3bf274ade55b5d15 *./usr/bin/PmNetConfigManager
      2edc15faf767d2c251559c9626e5703a *./etc/event.d/PmNetConfigManager
    root@palm-webos-device: md5sum /etc/event.d/PmNetConfigManager
      2edc15faf767d2c251559c9626e5703a  /etc/event.d/PmNetConfigManager
    Can anyone tell me if what I have is correct, or should I doctor?
    Bear with me, but I think what I'm looking for is for the files to match, and it appears to me that the PmNetConfigManager files match, but the LunaSysMgr doesn't.
    I was following this same line of questions back on pages 21-22, but still unsure if I even did the check correctly. And my LunaSysMgr doesn't match what Rod has on his device from back on page 18.

    Thanks again for any advice,
    JB
    Here are the md5sums for all the webOS versions of LunaSysMgr that I have access to:

    Code:
    rwhitby@karmic:/srv/doctors/build-info$ md5sum */rootfs/usr/bin/LunaSysMgr
    7530a093ce5b33f14e17723a12b4ea98  webosdoctorp100ewwbellmo-1.1.0/rootfs/usr/bin/LunaSysMgr
    f0253755ad62c3e0cad315ba22bab699  webosdoctorp100ewwbellmo-1.2.0/rootfs/usr/bin/LunaSysMgr
    ce8ab50242283ea66592d5380041de2d  webosdoctorp100ewwbellmo-1.2.1/rootfs/usr/bin/LunaSysMgr
    ee291d3c5a91cf9b7a1a3bbff16a42ec  webosdoctorp100ewwbellmo-1.3.1/rootfs/usr/bin/LunaSysMgr
    dea90948f6841a85b0efa4c13d966267  webosdoctorp100ewwbellmo-1.3.5.1/rootfs/usr/bin/LunaSysMgr
    5b4fe9f90833412e9cdbfefe4114e7b9  webosdoctorp100ewwbellmo-1.3.5/rootfs/usr/bin/LunaSysMgr
    af9f1883e7b1f07e479d120971e99c58  webosdoctorp100ewwbellmo-1.4.0/rootfs/usr/bin/LunaSysMgr
    8332a5dfd5df08ec5dbe8aecb79882e1  webosdoctorp100ewwbellmo-1.4.1/rootfs/usr/bin/LunaSysMgr
    b3d3752eacbe4821231494c3b4c9a64a  webosdoctorp100ewwsprint-1.0.3/rootfs/usr/bin/LunaSysMgr
    7530a093ce5b33f14e17723a12b4ea98  webosdoctorp100ewwsprint-1.1.0/rootfs/usr/bin/LunaSysMgr
    f0253755ad62c3e0cad315ba22bab699  webosdoctorp100ewwsprint-1.2.0/rootfs/usr/bin/LunaSysMgr
    ce8ab50242283ea66592d5380041de2d  webosdoctorp100ewwsprint-1.2.1/rootfs/usr/bin/LunaSysMgr
    ee291d3c5a91cf9b7a1a3bbff16a42ec  webosdoctorp100ewwsprint-1.3.1/rootfs/usr/bin/LunaSysMgr
    dea90948f6841a85b0efa4c13d966267  webosdoctorp100ewwsprint-1.3.5.1/rootfs/usr/bin/LunaSysMgr
    dea90948f6841a85b0efa4c13d966267  webosdoctorp100ewwsprint-1.3.5/rootfs/usr/bin/LunaSysMgr
    af9f1883e7b1f07e479d120971e99c58  webosdoctorp100ewwsprint-1.4.0/rootfs/usr/bin/LunaSysMgr
    ca6a3981c382b01a559d7186742f1fe5  webosdoctorp100ewwsprint-1.4.1.1/rootfs/usr/bin/LunaSysMgr
    6f7ad7484ebc7c93f6fe79114a0d7a5a  webosdoctorp100ewwtelcel-1.2.5/rootfs/usr/bin/LunaSysMgr
    dea90948f6841a85b0efa4c13d966267  webosdoctorp100ewwtelcel-1.3.5.1/rootfs/usr/bin/LunaSysMgr
    af9f1883e7b1f07e479d120971e99c58  webosdoctorp100ewwtelcel-1.4.0/rootfs/usr/bin/LunaSysMgr
    2afe7c221de5b5add2cf43f330eeb88f  webosdoctorp100eww-wr-1.1.3/rootfs/usr/bin/LunaSysMgr
    ee291d3c5a91cf9b7a1a3bbff16a42ec  webosdoctorp100ueu-wr-1.3.1/rootfs/usr/bin/LunaSysMgr
    dea90948f6841a85b0efa4c13d966267  webosdoctorp100ueu-wr-1.3.5.2/rootfs/usr/bin/LunaSysMgr
    2f47eacf33410729e3bc7c1a2b6c9859  webosdoctorp100ueu-wr-1.3.5/rootfs/usr/bin/LunaSysMgr
    af9f1883e7b1f07e479d120971e99c58  webosdoctorp100ueu-wr-1.4.0/rootfs/usr/bin/LunaSysMgr
    8332a5dfd5df08ec5dbe8aecb79882e1  webosdoctorp100ueu-wr-1.4.1/rootfs/usr/bin/LunaSysMgr
    dea90948f6841a85b0efa4c13d966267  webosdoctorp101ewwverizonwireless-1.3.5.1/rootfs/usr/bin/LunaSysMgr
    af9f1883e7b1f07e479d120971e99c58  webosdoctorp101ewwverizonwireless-1.4.0/rootfs/usr/bin/LunaSysMgr
    93506cdb38216f8f764fcc678cffefe3  webosdoctorp101ewwverizonwireless-1.4.1.1/rootfs/usr/bin/LunaSysMgr
    eaa20c9eb265db8bfe918d50f0d388d2  webosdoctorp120ewwsprint-1.3.5.1/rootfs/usr/bin/LunaSysMgr
    eaa20c9eb265db8bfe918d50f0d388d2  webosdoctorp121ewwverizonwireless-1.3.5.1/rootfs/usr/bin/LunaSysMgr
    7f404266baa15504631679ce70312c17  webosdoctorp121ewwverizonwireless-1.4.0/rootfs/usr/bin/LunaSysMgr
    bba51d18eadc8466b5b7c8ff700e93de  webosdoctorp121ewwverizonwireless-1.4.1.1/rootfs/usr/bin/LunaSysMgr
    de7b8729efd6f9f92e56ed2e29e5ab3f  webosdoctorp200ewwsprint-1.2.9.1/rootfs/usr/bin/LunaSysMgr
    124f822c8bcbb29febbb1397eb7edc15  webosdoctorp200ewwsprint-1.3.1/rootfs/usr/bin/LunaSysMgr
    496e32568db21dade6f8572b79273598  webosdoctorp200ewwsprint-1.3.2/rootfs/usr/bin/LunaSysMgr
    eaa20c9eb265db8bfe918d50f0d388d2  webosdoctorp200ewwsprint-1.3.5/rootfs/usr/bin/LunaSysMgr
    7f404266baa15504631679ce70312c17  webosdoctorp200ewwsprint-1.4.0/rootfs/usr/bin/LunaSysMgr
    bba51d18eadc8466b5b7c8ff700e93de  webosdoctorp200ewwsprint-1.4.1.1/rootfs/usr/bin/LunaSysMgr
    rwhitby@karmic:/srv/doctors/build-info$
    Your file matches:

    ca6a3981c382b01a559d7186742f1fe5 webosdoctorp100ewwsprint-1.4.1.1/rootfs/usr/bin/LunaSysMgr

    -- Rod
    Last edited by rwhitby; 05/07/2010 at 06:22 AM.
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  6. #466  
    I veg got it to work the uber kernel!

    But with 250 mhz sometimes the pre freez!

    Whats the best option to scale to have the best batterie life ?
  7. giftedmd's Avatar
    Posts
    43 Posts
    Global Posts
    91 Global Posts
    #467  
    Are there any plans to make the screenstate governor able to scale down to 250MHz or even 125MHz when the screen is off? My phone has no problem going that low and that would probably be really great for battery life and such.
  8. #468  
    I'm using screen state with it from 250-800mhz. It actually seems to run better compared to when I was using 500-800mhz. When I had it on those settings my phone would randomly hang/pause consistently. Now it seems with these new settings it performs more like the old .sh/.ipk install of the 800mhz kernal. Is using the screen state with 250-800mhz not recommended??
  9. #469  
    Two days ago I ran at the default 500 MHz all day just to establish a benchmark from it to the fixed 800 MHz I like to run. The actual time difference for opening a given app is minimal but the percentage of speed increase is close to 100%. And without question my Pre was more stable with the Performance 800 MHz Min/Max than it was in the default boot up config of 500. Same basic use pattern for both days, Music Player remix, a number of phone calls, text messages, emails, a few trips out to Preware Alpha to check for updates and new apps, a couple of app updates, test use of the camera, a little web surfing and a few stops in the Govnah to check the proc. temp.

    Govnah v0.2.5
    Uber Kernel v1.4.1-16


    500 MHz time for most apps to open = 2 seconds (pulse or glow around the icon on the card while the app loads = ~ 1 second).
    Two hang on wakeup with Luna Restart on each, one phone offline random issue that required a shutdown and restart, and overall not very smooth launcher operation all day.

    800 MHz time for most apps to open = 1 second or less (phone and email open instantly with no loading card at all)
    One hang on wakeup but no restart. Very smooth and snappy response with launcher and apps loading all day.

    Battery consumption and temperature were about the same for both days.

    Camera had a single screen pause with both settings at about 3-5 seconds after opening but then operated normally.

    That's about it.
  10. #470  
    Quote Originally Posted by unixpsycho View Post
    Running at 125 is unstable on some Pre.

    You can try powersave. it will not scale up fast at all which would in theory give better battery. the conservative governor is the best for battery and speed IMHO. but scaling in general will use more cycles so you wont see what you would think in battery life.
    What do you mean it uses more cycles? By having it set to conservative 250-800, should my battery be better? I notice minimal speed differences, still an improvement, not fantastic, but noticeable. And same with Battery. I unplugged it at 6:30, it's 10:30 and I still have 95% percent with a bit of facebook use and about 15 text messages. Should it be better than that?
  11. #471  
    Some Uber Kernel issues, When running it and going to the "app Catalog" all the icons do a constant refresh. I tried to switch covnah to all the different settings and it doesnt appear to make a difference, just they refresh faster of slower. Another issue is coming out of "sleep" Ill click the top right button and then go to slide the yellow lock up and I find that the phone hasn't been locked and its been running @ 800mhz. This is while I set Govnah to screenstate.
  12. #472  
    Quote Originally Posted by ProCision View Post
    Some Uber Kernel issues, When running it and going to the "app Catalog" all the icons do a constant refresh. I tried to switch covnah to all the different settings and it doesnt appear to make a difference, just they refresh faster of slower. Another issue is coming out of "sleep" Ill click the top right button and then go to slide the yellow lock up and I find that the phone hasn't been locked and its been running @ 800mhz. This is while I set Govnah to screenstate.
    First issue is a known issue. Go into preferences in Govnah and turn off the update launcher icon setting. This will stop the app catalog refresh. If you don't have this option, update Govnah application. If you've already tried this, then I have no idea, as mine works fine.
  13. lswartz33's Avatar
    Posts
    74 Posts
    Global Posts
    79 Global Posts
    #473  
    Quote Originally Posted by ProCision View Post
    Some Uber Kernel issues, When running it and going to the "app Catalog" all the icons do a constant refresh. I tried to switch covnah to all the different settings and it doesnt appear to make a difference, just they refresh faster of slower. Another issue is coming out of "sleep" Ill click the top right button and then go to slide the yellow lock up and I find that the phone hasn't been locked and its been running @ 800mhz. This is while I set Govnah to screenstate.
    Turn off the 'Update Launcher Icon' in the Preferences menu. There's a message next to it telling you the App Catalog will flicker if it is on.
  14. #474  
    Quote Originally Posted by Stevesrjr86 View Post
    I'm using screen state with it from 250-800mhz. It actually seems to run better compared to when I was using 500-800mhz. When I had it on those settings my phone would randomly hang/pause consistently. Now it seems with these new settings it performs more like the old .sh/.ipk install of the 800mhz kernal. Is using the screen state with 250-800mhz not recommended??
    No you're not. screenstate code does not allow the min CPU speed to be set. it is static at 500Mhz.
    Live free or DIE!
  15. #475  
    Quote Originally Posted by frishmans92 View Post
    What do you mean it uses more cycles? By having it set to conservative 250-800, should my battery be better? I notice minimal speed differences, still an improvement, not fantastic, but noticeable. And same with Battery. I unplugged it at 6:30, it's 10:30 and I still have 95% percent with a bit of facebook use and about 15 text messages. Should it be better than that?
    The ondemand, powersave, and conservative governors are huge in code size to be able to do dynamic scaling upon CPU load. each tick of the CPU clock is battery spent. So the more you use your phone the more battery. but switching quickly from one speed to another without bloated code is a battery saver. It sounds silly but in embedded terms it makes sense.
    Live free or DIE!
  16. #476  
    thanks for clearing that up. I know you said before conservative would be best for power and battery, but with what settings exactly?
  17. #477  
    For those with camera problems please try the -21 release available now.
    Live free or DIE!
  18. #478  
    Quote Originally Posted by Stevesrjr86 View Post
    thanks for clearing that up. I know you said before conservative would be best for power and battery, but with what settings exactly?
    I only mess with the up-threshold to 20-30 and scale from 500.
    Live free or DIE!
  19. xtn
    xtn is offline
    xtn's Avatar
    Posts
    434 Posts
    Global Posts
    711 Global Posts
    #479  
    Release -21 does appear to have whipped the camera back into shape, at least with just a four pic test.

    I'm curious what the issue was?
  20. #480  
    Quote Originally Posted by xtn View Post
    curious what the issue was?

    Tap the Kernel's icon in your launcher. You answer is in the Changelog. :-)


    M.

Posting Permissions