Reply
Thread Tools
Morpog's Avatar
Posts: 956 | Thanked: 2,628 times | Joined on Nov 2011
#361
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.

Last edited by Morpog; 2014-03-15 at 18:32.
 

The Following 14 Users Say Thank You to Morpog For This Useful Post:
Posts: 277 | Thanked: 285 times | Joined on Dec 2011 @ Poland
#362
If it's gone after a reboot I'm trying it!
 
zlatko's Avatar
Posts: 861 | Thanked: 936 times | Joined on Feb 2010 @ Bulgaria
#363
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.
 

The Following User Says Thank You to zlatko For This Useful Post:
Posts: 277 | Thanked: 285 times | Joined on Dec 2011 @ Poland
#364
It's a nice thing to do before showing somebody your Jolla for the first time. It does make all transitions very smooth.
 

The Following 2 Users Say Thank You to szymeczek34 For This Useful Post:
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#365
Tbh am just hoping for a few more optimizations between the Android drivers and Sailfish
 
aironeous's Avatar
Posts: 819 | Thanked: 806 times | Joined on Jun 2009 @ Oxnard, Ca.
#366
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
__________________
On duh count uh tree
 

The Following 2 Users Say Thank You to aironeous For This Useful Post:
chenliangchen's Avatar
Posts: 1,478 | Thanked: 9,871 times | Joined on Dec 2008 @ Shanghai / London
#367
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.
 

The Following User Says Thank You to chenliangchen For This Useful Post:
Dave999's Avatar
Posts: 7,075 | Thanked: 9,073 times | Joined on Oct 2009 @ Moon! It's not the East or the West side... it's the Dark Side
#368


3 days to gogo
__________________
Do something for the climate today! Anything!

I don't trust poeple without a Nokia n900...
 
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#369
That picture's sooo outdated nowadays, we need the new CEO wearing a batman mask whilst he's holding the Sailfish.
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#370
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.
 

The Following 14 Users Say Thank You to For This Useful Post:
Reply

Tags
"soon", "sooner", "when?"


 
Forum Jump


All times are GMT. The time now is 20:45.