Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Sailfish now on 1.0 (Jolla MWC announcement)

    Reply
    Page 37 of 72 | Prev | 27   35     36   37   38     39   47 | Next | Last
    Morpog | # 361 | 2014-03-15, 18:18 | Report

    Originally Posted by TMavica View Post
    anyone know change the governor can make the ui faster

    do it as root

    echo "performance" >/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/pwrscale/trustzone/governor

    Originally Posted by Dared View Post
    Huh?

    10chars
    That tweak is from IRC channel, by stskeeps, which is Jolla's man for technical research. Yes it does work. After that the device feels smooth like butter. I am using this last 3 days already. Battery lasts a bit less, but still much better than with the NFC bug

    Try it. You will be surprised. It's gone after a reboot.

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by Morpog; 2014-03-15 at 18:32.
    The Following 14 Users Say Thank You to Morpog For This Useful Post:
    aegis, chenliangchen, Daneel, Dared, ezameht, Jordi, Manatus, MartinK, mattaustin, pycage, rcolistete, rentze, sbock, zlatko

     
    szymeczek34 | # 362 | 2014-03-15, 18:44 | Report

    If it's gone after a reboot I'm trying it!

    Edit | Forward | Quote | Quick Reply | Thanks

     
    zlatko | # 363 | 2014-03-15, 18:48 | Report

    It really makes UI smoother. It is setting the GPU to max frequency. It may be possible to revert with using "ondemand" setting instead "performance" one.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to zlatko For This Useful Post:
    richardski

     
    szymeczek34 | # 364 | 2014-03-15, 18:55 | Report

    It's a nice thing to do before showing somebody your Jolla for the first time. It does make all transitions very smooth.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to szymeczek34 For This Useful Post:
    jmsarriat, richardski

     
    m4r0v3r | # 365 | 2014-03-15, 20:51 | Report

    Tbh am just hoping for a few more optimizations between the Android drivers and Sailfish

    Edit | Forward | Quote | Quick Reply | Thanks

     
    aironeous | # 366 | 2014-03-15, 23:59 | Report

    Has anyone tried the Moga Game controller on the Jolla phone yet? I have one for my HTC One and it works pretty good. Lots of touchy touchies. http://www.mogaanywhere.com/

    I suddenly remembered something about android apps not having access to bluetooth
    I wonder if the upcoming update will make Android games work with bluetooth,

    I wonder if Jolla will incorporate that new speed reading tech called spritz in their OS anywhere in future updates because I heard on the radio the Samsung Galaxy S5 will have it.
    http://hereandnow.wbur.org/2014/03/1...-speed-reading

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to aironeous For This Useful Post:
    MartinK, richardski

     
    chenliangchen | # 367 | 2014-03-16, 00:03 | Report

    Originally Posted by Morpog View Post
    That tweak is from IRC channel, by stskeeps, which is Jolla's man for technical research. Yes it does work. After that the device feels smooth like butter. I am using this last 3 days already. Battery lasts a bit less, but still much better than with the NFC bug

    Try it. You will be surprised. It's gone after a reboot.
    I wish there is a tweak to make it work after reboot, it makes such a differenct that I prefer sacrifising battery.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to chenliangchen For This Useful Post:
    richardski

     
    Dave999 | # 368 | 2014-03-16, 07:50 | Report



    3 days to gogo

    Edit | Forward | Quote | Quick Reply | Thanks

     
    jalyst | # 369 | 2014-03-16, 09:38 | Report

    That picture's sooo outdated nowadays, we need the new CEO wearing a batman mask whilst he's holding the Sailfish.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    nieldk | # 370 | 2014-03-16, 10:34 | Report

    For those interrested

    https://openrepos.net/content/nieldk/cpufrequtils and
    https://openrepos.net/content/nieldk/libsysfs

    Code:
    [root@localhost nemo]# cpufreq-info 
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to http://bugs.opensuse.org, please.
    analyzing CPU 0:
      driver: msm
      CPUs which run at the same hardware frequency: 0
      CPUs which need to have their frequency coordinated by software: 0
      maximum transition latency: 0.00 ms.
      hardware limits: 384 MHz - 1.40 GHz
      available frequency steps: 384 MHz, 432 MHz, 486 MHz, 540 MHz, 594 MHz, 648 MHz, 702 MHz, 756 MHz, 810 MHz, 864 MHz, 918 MHz, 972 MHz, 1.03 GHz, 1.08 GHz, 1.13 GHz, 1.19 GHz, 1.24 GHz, 1.30 GHz, 1.35 GHz, 1.40 GHz
      available cpufreq governors: msm-dcvs, interactive, ondemand, userspace, powersave, performance
      current policy: frequency should be within 384 MHz and 1.40 GHz.
                      The governor "ondemand" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 384 MHz:88.26%, 432 MHz:0.10%, 486 MHz:0.13%, 540 MHz:0.13%, 594 MHz:0.10%, 648 MHz:0.17%, 702 MHz:0.11%, 756 MHz:0.08%, 810 MHz:0.07%, 864 MHz:0.05%, 918 MHz:1.96%, 972 MHz:0.04%, 1.03 GHz:1.85%, 1.08 GHz:0.02%, 1.13 GHz:0.02%, 1.19 GHz:0.02%, 1.24 GHz:0.02%, 1.30 GHz:0.01%, 1.35 GHz:0.02%, 1.40 GHz:6.82%  (112062)
    analyzing CPU 1:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 0.00 ms.
    Code:
    [root@localhost nemo]# cpufreq-set -g performance
    [root@localhost nemo]# cpufreq-info 
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to http://bugs.opensuse.org, please.
    analyzing CPU 0:
      driver: msm
      CPUs which run at the same hardware frequency: 0
      CPUs which need to have their frequency coordinated by software: 0
      maximum transition latency: 0.00 ms.
      hardware limits: 384 MHz - 1.40 GHz
      available frequency steps: 384 MHz, 432 MHz, 486 MHz, 540 MHz, 594 MHz, 648 MHz, 702 MHz, 756 MHz, 810 MHz, 864 MHz, 918 MHz, 972 MHz, 1.03 GHz, 1.08 GHz, 1.13 GHz, 1.19 GHz, 1.24 GHz, 1.30 GHz, 1.35 GHz, 1.40 GHz
      available cpufreq governors: msm-dcvs, interactive, ondemand, userspace, powersave, performance
      current policy: frequency should be within 384 MHz and 1.40 GHz.
                      The governor "performance" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 384 MHz:88.25%, 432 MHz:0.10%, 486 MHz:0.13%, 540 MHz:0.13%, 594 MHz:0.10%, 648 MHz:0.17%, 702 MHz:0.11%, 756 MHz:0.08%, 810 MHz:0.07%, 864 MHz:0.05%, 918 MHz:1.96%, 972 MHz:0.04%, 1.03 GHz:1.85%, 1.08 GHz:0.02%, 1.13 GHz:0.02%, 1.19 GHz:0.02%, 1.24 GHz:0.02%, 1.30 GHz:0.01%, 1.35 GHz:0.02%, 1.40 GHz:6.83%  (112129)
    analyzing CPU 1:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 0.00 ms.
    Code:
    [root@localhost nemo]# cpufreq-set -g powersave
    [root@localhost nemo]# cpufreq-info 
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to http://bugs.opensuse.org, please.
    analyzing CPU 0:
      driver: msm
      CPUs which run at the same hardware frequency: 0
      CPUs which need to have their frequency coordinated by software: 0
      maximum transition latency: 0.00 ms.
      hardware limits: 384 MHz - 1.40 GHz
      available frequency steps: 384 MHz, 432 MHz, 486 MHz, 540 MHz, 594 MHz, 648 MHz, 702 MHz, 756 MHz, 810 MHz, 864 MHz, 918 MHz, 972 MHz, 1.03 GHz, 1.08 GHz, 1.13 GHz, 1.19 GHz, 1.24 GHz, 1.30 GHz, 1.35 GHz, 1.40 GHz
      available cpufreq governors: msm-dcvs, interactive, ondemand, userspace, powersave, performance
      current policy: frequency should be within 384 MHz and 1.40 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 384 MHz (asserted by call to hardware).
      cpufreq stats: 384 MHz:88.23%, 432 MHz:0.10%, 486 MHz:0.13%, 540 MHz:0.13%, 594 MHz:0.10%, 648 MHz:0.17%, 702 MHz:0.11%, 756 MHz:0.08%, 810 MHz:0.07%, 864 MHz:0.05%, 918 MHz:1.96%, 972 MHz:0.04%, 1.03 GHz:1.85%, 1.08 GHz:0.02%, 1.13 GHz:0.02%, 1.19 GHz:0.02%, 1.24 GHz:0.02%, 1.30 GHz:0.01%, 1.35 GHz:0.02%, 1.40 GHz:6.85%  (112130)
    analyzing CPU 1:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 0.00 ms.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 14 Users Say Thank You to For This Useful Post:
    48GX, Daneel, dirkvl, Jordi, Makeclick, Manatus, MartinK, rcolistete, sbock, shallimus, szymeczek34, TMavica, zlucoblij, ZogG

     
    Page 37 of 72 | Prev | 27   35     36   37   38     39   47 | Next | Last
vBulletin® Version 3.8.8
Normal Logout