İletişim


 Android indir


admin@444android.com


admin@444android.com

×

Selamun Aleykum Arkadaslar, Ne yazik ki cok az sayida Turk developerlarimiz var. bu yuzden az da olsa size ***** araciligi ile birkaç sey ogretmeye calisacagim. Ilk *****muz Nelerin gerektigi hakkinda olacaktir. (Modifye etmek icin) ve ayniz zamanda ornek olarak da Statusbar transparantligini anlatiyorum :) Bir istek arzunuz olursa soyleyin, zamanim oldugunda onuda gostermeye/ogretmeye calisirim. Haydi Bismillah.

Bu konu 13221 kez görüntülendi 37 yorum aldı ...
【T U T O R I A L 】 ★ DroidTurK ★ ---- Development! 13221 Reviews

    Konuyu değerlendir: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    5 üzerinden | Toplam: 0 kişi oyladı ve 13221 kez incelendi.

Sayfa 1 Toplam 4 Sayfadan 123 ... Sonuncu
  1. #1
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    facebook müşteri hizmetleri
    teknoloji destek
    Selamun Aleykum Arkadaslar,


    Ne yazik ki cok az sayida Turk developerlarimiz var. bu yuzden az da olsa size ***** araciligi ile birkaç sey ogretmeye calisacagim.

    Ilk *****muz Nelerin gerektigi hakkinda olacaktir. (Modifye etmek icin) ve ayniz zamanda ornek olarak da Statusbar transparantligini anlatiyorum

    Bir istek arzunuz olursa soyleyin, zamanim oldugunda onuda gostermeye/ogretmeye calisirim.

    Haydi Bismillah.



    Konu Emre tarafından (10.07.13 Saat 10:29 ) değiştirilmiştir.

  2. #2
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Selamun Aleykum Arkadaslar,

    Bu *****da sizlere "Wallpaper Scrolling"i nasil elde edeceginizi gosterecegim. bu mod'u her launcher'e uygulaya bilirsiniz


    Ben Bu *****da ubuntuyu kullaniyorum yalniz siz *****da ifade ettigim gibi Windowsda "Apk-Multi-tool"u kullana bilirsiniz.

    zaten onu nasil kullanacaginizi *****1de gosterdim )



    Konu AskinSavascisi tarafından (12.07.13 Saat 18:35 ) değiştirilmiştir. Sebep: Wallpaper Scrolling Tutorial

  3. #3
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    How to: UNROOT

    Eger telefonunuzu geri garantiye verecekseniz yapmaniz gereken seyler!

    Konu AskinSavascisi tarafından (15.07.13 Saat 19:33 ) değiştirilmiştir.

  4. #4
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    *****4 ... Benim ))

  5. #5
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    ***** 5.. nthego:

  6. #6
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    ***** 6.. Daha cok *****larimiz olacak insallah DD

  7. #7
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Simdilik Bu kadar yeter.. Galiba

  8. #8
    Emre - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    09.03.2012
    Nereden
    İstanbul
    Mesajlar
    22.699
    @Emre

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    konu ayrı foruma taşındı


    • Samsung Galaxy Note 5 | Silver Titan | 5.1.1 | 5.7" QHD | 518 ppi | CMOS 16MP UHD 4K | 128 Bit Exynos 7420 Octa | 4GB |
    • Monster Abra A5 5.1.1 | i7-4720HQ | 2GB GDDR5 GTX960M | FHD 15.6" Mat Led IPS | 750GB 7400RPM + 120 GB SSD | 8GB DDR3 1600Mhz
    • LG 55LA660S & Digiturk +plus IQ | 55" 140cm | 1920x1080 Smart 3D FHD LED plus | MCI 400Hz | Cinema Screen | 0,9 Ghz Dual Core |
    • Samsung UE42F5570 & Turkcell TV+ | 42" 106cm | 1920x1080 Smart HD LED | Dual Core | Clean View | 100Hz |
    • Ford Fiesta 1.25 Trend 5K LPG | 2010 | 82hp | 76000 Km |




    [LIST][*]444Android.com
    [*][COLOR=#ff0000]

  9. #9
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Selamun Aleykum Arkadaslar,

    Batarya, Ekran saati, Kernel hakkinda birkac sorusu olan arkadaslarim buyrun bunu okusunlar (biraz uzun )



    Android kullanan cogu arkadasimiz ilk basta olmasada bir zaman sonra "Flash maniac" oluyor.. yeni birseyler denemeden duramiyor.

    Bazen yeni bir kernel flashladiktan sonra meraak ediyoruz ki:

    1. "Tamam ben simdi bu yeni abcd kernel'i flashladyim, butun bu "Governor" ne anlama geliyor? ne ise yariyor? hangisinin benim icin daha iyi oldugunu nerden bilecegim? onlarda nasil tweak uygularim?"


    2. "Bircok kisi Module diyip duruyor, nedir bu kernel'in icinde ki modul? onlari nasil kullanirim? onlari es gecmek acaba sorun yaratir mi?


    3. "bir I/O scheduler ne rol oynuyor telefonumuzda? hangisi iyi?"

    4. "Cpu'yu kendim ayarlaya bilirmiyim? neler degistire bilirim? vs vs"


    Bu konuda governor, module, I/O scheduler'u ele alacagim ve Umarim bu konu sizin bircok sorunuza cevap olacaktir


    1. GOVERNOR

    I) Kilavuz

    (19tane Governor vardir)


    1) Ondemand
    2 Ondemandx
    3) Conservative
    4) Interactive
    5) Interactivex
    6) Lulzactive
    7) Lulzactiveq
    8) Smartass
    9) SmartassV2
    10) Intellidemand
    11) Lazy
    12) Lagfree
    13) Lionheart
    14) Lionheartx
    15) Brazilianwax
    16) SavagedZen
    17) Userspacce
    18) Powersave
    19) Performance


    Not: Pegasusq ise samsung'un kendi ozel multi-core governorudur






    1) Ondemand:

    Bircok Kernellerde varsayilan governor. Ondemand'in en buyuk "ozelligi" ise hafif bir cpu kullanimi fark ettigi zaman en kisa zamanda MAX CPU'ye gecmektir, boylece system'in akiciligina sebep olur. en kucuk cpu hizi gerektiren islemlerde bile drek max'a cikar.


    2) Ondemandx:

    Aynisi sadece biraz daha batarya tasaruflu. Ekran kapali oldugunda MAX frekans 500mhz dusuyor. Ondemand ve ondemandx'e aslinda stabil bir governor diye biliriz

    yalniz bircok kernel kisa bir surede minden max'a veya max frekans hizinden min'e inme ozelligine sahip olmadigi icin bu governorlari cok nadir goreceksiniz.


    3) Conservative:

    Ondemand uzerine baze edilmis yalniz biraz daha yavas calisoyor, ondemand gibi en hafif cpu gerektiren islemde hemen MAX frekans hizina cikmaz. yavas yavas seviye atlar ( ornegin, 100-200 -300 -500-800 ...).


    4) Interactive:

    cok daha hizli bir ondemand governor olarak dusune bilirsiniz. cok hizli cevap verir yalniz bataryanizida o kadar azaltir. Interactive governor'u aniden cok guc gerektiren seyler icin uretilmistir. ornegin sadece whatsapp kullaniyorsunuz aniden , caniniz NFS oynamak istedi ayni zamanda facebook ve bir arama yapiyorsunuz.. butur seyler icin interactive iyi bir governor secimi.


    5) Interavtivex:

    Aynisi sadece wake profili biraz daha hafifletilmis (frekans gecisleri), ve daha az batarya kullaniyor.

    6) Lulzactive:

    Tegrak Lulzactive'i , Interactive ve Smartass uzerine baz etmistir. Favorilerden birtanesidir (lulz)

    Lulzactivede kullanicinin kendisi herseyi (her adimi) seciyor. ne zaman ne kadar calisacagini, hangi hizda vs vs.. inc_cpu_load, pump_up_step..


    Ornegin:

    inc_cpu_load=70
    pump_up_step=2
    pump_down_step=1
    If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
    If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.



    Lulzactiveq:

    lulzactiveq ise xda uyesi olan robertobsc tarafindan modifye ve siyah kernel'e gore adapte edilmistir. (G2 - G3)

    lulzactiveq, extradan bir parameter vererek (dec_cpu_load) lulzactive'i daha bir seviyeye tasimaya calismistir.

    Aslinda lulzactive serisini , pegasusqnun (samsung) modifye edilip daha ust bir seviyeye cikartilmis hali olarak dusune bilirsiniz



    8) Smartass

    Erasmux, interactive sourc'u yeniden yazip smartass governor'u ortaya cikartmistir. ana hedef ise batarya surecini cogaltip ve bunu yaparkende performansi etkilememek.


    9) Smartassv2

    Smartassv2, bir favori daha .. burda ki amac ise her isleme gore "ideal frekansi" bulmaktir. ekran acik ve kapaliyken degisik frekans hizlarina sahip ola bilirsiniz boylecelikle batarya daha uzun sure gider. (DEEP SLEEP icin cok iyi)

    yani kisace, batarya ve performans arasinda ki mukemmeligi sagliyor. (calisiyor daha dogrusu )


    10) Intellidemand:

    bir diger adi ile Intelligent Ondemand , kuran Faux. buda ondemand uzerine baz edilmistir. bu governor anlatimi ise cok basit.

    Intelligent = akilli. Siz telefonunuz nasil kullaniyorsaniz governor ona gore ayarlaniyo, ayarliyor kendisini..

    anlatacak pek birsey yok bu governor daha cok GPU uzerine calisiyor. ve bataryayi koruyor.



    11) Lazy:

    Ezekeel'in kurmus oldugu Lazy governor'u ise aslinda tam bir ondemand governor'u sadece birkac parameter eklenilmis: min_time_state, CPUnun kullandigi minimumden bir uste frekansa cikmak izin zaman.

    Lazyde bircogun yaptigi hata ise parameterleri yanlis ayarlayip CPUnun hep MAX frekansda olmasini sagliyor. boylecede batarya . . . (nokta nokta nokta )



    12) Lagfree:

    Lagfree ondemand'in bir benzeri, tek amaci ise en yuksek performansda en az batarya harcamasi saglamak.


    13) Lionheart:

    Samsung'un update3source uzerine baze edilmistir. pek ozel birsey yok anlatacak.. performansi saglamak icin bir governor daha..

    lionhear ayarlari:

    ampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
    up_threshold:60
    down_threshold:30
    freq_step:5
    Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.

    14) LionheartX: Batarya icin tekrardan ayarlanmis (daha az kullansin diye)


    15) Brazilianwax:

    SmartassV2'in bir benzeri, rampingde daha cok agresif yani daha yuksek performans ve ne yazik ki az batarya (ekran saati).


    16) SavagedZen:

    smartassv2 uzerine baze edilmis bir governor daha.. amaci performans ve batarya arasinda ki balansi saglamak (bu konuda brazillianwaxdan daha iyi)


    17) Userspace:

    Bu governorde ise, Kullanicinin kendisi Frekans hizlarini seciyor. (normalde otomatik/digerlerinde)


    18) Powersaver:

    MAX frekans'i , min frekansina gore ayarliyor boylece bataryaniz cok UZUN gidiyor ama telefonda baya lagliyor


    19) Performance:

    Min frekansi , max frekansa ayarliyor.. boylece alabileceginiz en iyi performansi aliyorsunuz telefonunuzdan.



    OZET:

    Sizinde farkettiginiz gibi Governorler 3 veya 4 kategoriye ayarlanirlar:

    1) Ondemand uzerine base edilmisler

    2) Conservative uzerine base edilmisler

    3) Interactive uzerine "

    [4] Degisik/ Tuaf governorler: userspace, Powersave, Performance



    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    S: Tamam yeterince Anlatmaya Calistin AskinSavascisi ama simdi hangisi Performance ve hangisi batarya icin iyi ??

    C: Zor bir soru ama Lulzactive ve SmartassV2 performans ve batarya arasinda iyi bir balans sagliyor.

    Lulzactive batarya ve performans icin az daha iyi ))


    S: Peki nasil Governor Degistirirm?

    C: Bazi kernellerin kendisi sana secenek sunuyor STWEAKS ayarlarin icinde, eger yoksa kendin manuel (init.d tarafindan) yapacaksin.

    kod:
    Kod:
    echo "governor-name" > /sys/devices/system/cpu/cpu0/cpufreq /scaling_governor

    S: Peki ozaman benim icin hangi governor iyi?

    C: Telefonundan ne bekledigine bagli, eger hem performans hem batarya istiyorsan ozm Lulzactive'i oneririm


    S: Governor degistirdim, veya yeni bir rom/kernel yukledim ama bazen (cok nadir) telefon takiliyor..

    C: Unutmayin ki biz profesyonel programcilar degiliz.. olsaydik burda olmazdik .. Alt ustu reboot yapip gecin, okadarda buyuk bir sorun degil.

    Eger nadir degilde, sik sik takiliyorsa ozaman size ROM/kernel degistirmenizi tavsiye ederim.


    S: hicbir governor benim isteklerime uymuyor. birtanesini kendim tweak yapmak istiyorum,, nasil??

    C: Tamam, Init.d script sayesinde yapa bilirsiniz echo kommand'i kullanarak.

    Kod:
    /sys/devices/system/cpu/cpufreq/name-of-active-governor/name-of-the-paramater-to-tweak
    Orgenig:

    Kod:
    echo "20000" /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time

  10. #10
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Part 2: Governor Tweakleri

    III) PARAMETERLER & TWEAKS:

    [Sadece Ondemand, Conservative, SmartassV2, Lulzactive ve Interactive; en cok secilen/kullanilan governorler.]

    Her governor'un kendine gore ayarlari vardir, ama sonucta hepsinde yaklasik ayni yontem var.





    1.ONDEMAND


    [ PARAMETERS ]

    i) sampling_rate - Measured in uS , this is how often the kernel look at the CPU usage and make decisions on what to do about the frequency. Higher values means CPU polls less often. For lower frequencies, this could be considered an advantage since it might not jump to next frequency very often, but for higher frequencies, the scale-down time will be increased.


    ii) up_threshold - Measured in percentage 1-100, When CPU load reaches this point, governor will scale CPU up. Higher value means less responsiveness and lower values corresponds to more responsiveness at the cost of battery.


    iii) powersave_bias - Default value is 0. Setting a higher value will bias the governor towards lower frequency steps. Use this if you want CPU to spend less time on higher frequencies. A better alternative would be to underclock to a lower frequency than using powersave bias.


    iv) sampling_down_factor - In the simplest form, sampling_down_factor determines how often CPU should stay at higher frequencies when truly busy. Default behavior is fast switching to lower frequencies (1). Having sampling_down_factor set to 1 makes no changes from existing behavior (for the non-modified ondemand), but having sampling_down_factor set to a value greater than 1 causes it to act as a multiplier for the scheduling interval for re-evaluating the load when the CPU is at its highest clock frequency (which is scaling_max_freq) due to high load. This improves performance by reducing the overhead of load evaluation and helping the CPU stay at its highest clock frequency when it is truly busy, rather than shifting back and forth in speed. This tunable has no effect on behavior at lower frequencies/lower CPU loads.


    v) down_differential - This factor indirectly calculate the 'down-threshold' of Ondemand. After completing sampling-down-factor*sampling-rate at max frequency because of high load, governor samples the load again to calculate an estimate of the new target frequency in a way that the lowest frequency will be chosen that would not trigger up_threshold in the next sample. Because triggering up-threshold will again cause CPU to scale up to max frequency. During this choice down_differential is taken into account as a breathing room value. Target frequency is calculated as max_load_freq / (up_threshold - down_differential). The obtained value might be a non-existent value in the freq_table and CPU driver will round it off to a value in freq_table. max_load_freq is the theoretical frequency at which CPU can handle 100% workload. It is usually a value below scaling_max_freq. See this post by AndereiLux for more info.




    vi) freq_step - Whenever up-scaling logic is triggered the governor instructs the CPU to raise its frequency by freq_step percentage of max allowed frequency. (max policy * (freq step / 100)). Ex: max policy is 1600 and freq step 21%, it will scale 1600 * 21% = 336. We have a 100MHz grained frequency table so it rounds up to the next 100MHz, hence 336 becomes 400. So say we're idling at 200MHz and the up-scaling logic gets triggered with the above settings, the next frequency will be 600MHz. Note that freq_step and smooth_scaling does pretty much the same thing.



    [ SAMPLE TWEAKS ]
    i) For battery:-

    To bias ondemand towards battery saving, set high up-thresholds and higher sampling-rate. This way, governor polls less often and scales up less often.
    Code:

    echo "95" /sys/devices/system/cpu/cpufreq/ondemand/up_thresholdecho "120000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rateecho "1" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factorecho "5" > /sys/devices/system/cpu/cpufreq/ondemand/down_differentialecho "10" > /sys/devices/system/cpu/cpufreq/ondemand/freq_step
    ii) For performance:-

    To bias ondemand towards performance, set low up-thresholds and lower sampling-rate. This way, governor polls more often and scales up quite often.
    Code:

    echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_thresholdecho "50000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rateecho "2" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factorecho "15" > /sys/devices/system/cpu/cpufreq/ondemand/down_differentialecho "50" > /sys/devices/system/cpu/cpufreq/ondemand/freq_step


    2.LULZACTIVE

    1. Initial Version:-
    [ PARAMETERS ]
    i) down_sampling_time - Sampling time to scale cpu down.
    ii) up_sampling_time - Sampling time to scale cpu up.


    [ SAMPLE TWEAKS ]
    Unfortunately, the initial version of lulzactive doesn't give user much control on it's behavior. We can only control how often cpu should scale up and scale down. Usehigher down_sampling_time if you experience lag while scrolling through browser, app drawer, etc. Better keep the default up_sampling time (24000) unchanged. And make down_sampling proportional to up_sampling. Like 2x24000=48,000 or 3x24000=72000.


    2. Second Version
    :-
    [ PARAMETERS ]
    i) inc_cpu_load - In previous version, this was 'hard-coded' to 60. Now it's user-configurable. The frequency at which governor scales CPU up/down. Load < inc_cpu_load: cpu scaled down. Load >= inc_cpu_load: cpu scaled up

    ii) pump_up_step
    - No of scale up steps when load >= inc_cpu_load

    iii) pump_down_step -
    No of scale down steps when load < inc_cpu_load


    iv) screen_off_min_step -
    Steps in frequency table to be used when screen-off. Example: If available freqs are 1600 1400 1200 1000 800 500 200 100 (L0 to L7) and screen_off_min_step=5 then 100,200 and 500 (L5 to L7) will be used during screen-off depending on the demand.


    v) up_sample_time -
    same as initial version. (Allowed values 10,000 to 50,000)


    vi) down_sample_time -
    same as older version. (Allowed values 10,000 to 100,000)


    [ SAMPLE TWEAKS ]
    i) For battery:-
    Code:

    echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_loadecho "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_stepecho "2" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_stepecho "50000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_timeecho "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_timeecho "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
    This tweak cause lulzactive gradually scale up CPU and rapidly scale down on low load.

    ii) For performance:-

    Code:

    echo "60" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_loadecho "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_stepecho "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_stepecho "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_timeecho "70000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_timeecho "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
    This tweak cause lulzactive scale up CPU rapidly, polling often and scale down gradually.
    iii) For balanced-performance:-
    Code:

    echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_loadecho "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_stepecho "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_stepecho "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_timeecho "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_timeecho "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
    This tweak cause lulzactive to poll more often and scale up 4 steps above current frequency, but only at 90% load. CPU is scaled down normally.
    note: If you're lazy to use a script, use lulzactive app from market to tweak the governor. https://market.android.com/details?i...rak.lulzactive


    3.SMARTASSV2

    [ PARAMETERS ]

    i) awake_ideal_freq -
    The frequency until which CPU is scaled up rapidly on screen-awake (from sleep). Thereafter, scaling up is less aggressive.


    ii) sleep_ideal_freq -
    The frequency until which CPU is scaled down rapidly when screen is turned off. Thereafter, scaling down is less aggressive.


    iii) up_rate_us -
    The minimum amount of time to spend at a frequency before we can ramp up. (Ignored below awake-ideal frequency since governor needs to rapidly scale up to awake_ideal_freq when below it)

    iv) down_rate_us -
    The minimum amount of time to spend at a frequency before we can ramp down. (Ignored above sleep-ideal frequency since governor needs to rapidly scale down to sleep_ideal_freq when above it)

    v) max_cpu_load -
    Same as up_threshold in other governors.

    vi) min_cpu_load -
    Same as down_threshold in other governors.

    vii) ramp_down_step -
    Frequency delta when ramping down below the ideal frequency. Zero disables and will calculate ramp down according to load heuristic. When above the ideal frequency we always ramp down to the ideal freq.

    viii) ramp_up_step -
    Frequency when ramping up above the ideal frequency. Zero disables and causes to always jump straight to max frequency. When below the ideal frequency we always ramp up to the ideal freq.

    ix) sleep_wakeup_freq -
    The frequency to set when waking up from sleep. When sleep_ideal_freq=0 this will have no effect.


    [ SAMPLE TWEAKS ]
    i) For battery:-
    Code:

    echo "500000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq;echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;echo "500000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freqecho "85" > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load;echo "70" > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load;echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step;echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step;echo "48000" > /sys/devices/system/cpu/cpufreq/smartass/up_rate_usecho "49000" > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us
    ii) For performance:-
    Code:

    echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq;echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freqecho "75" > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load;echo "45" > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load;echo "0" > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step;echo "0" > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step;echo "24000" > /sys/devices/system/cpu/cpufreq/smartass/up_rate_usecho "99000" > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us

    4.CONSERVATIVE


    [ PARAMETERS ]
    i) down_threshold, ii) up_threshold, iii) sampling_down_factor, iv) sampling_rate - Refer above governors.

    v) freq_step
    - Defines how much (as a percentage of the maximum CPU speed) the conservative governor will increase the CPU speed by each time the CPU load reaches the Up Threshold.


    [ SAMPLE TWEAKS ]
    i) For battery:- [Set freq_step to lower value to make conservative governor conserve more battery]
    Code:

    echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_thresholdecho "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rateecho "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factorecho "40" > /sys/devices/system/cpu/cpufreq/conservative/down_thresholdecho "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step


    ii) For performance:-
    [Isn't it ironical that we are tuning Conservative to achieve blazing performance!]
    Code:

    echo "60" > /sys/devices/system/cpu/cpufreq/conservative/up_thresholdecho "40000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rateecho "5" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factorecho "20" > /sys/devices/system/cpu/cpufreq/conservative/down_thresholdecho "25" > /sys/devices/system/cpu/cpufreq/conservative/freq_step


    5.INTERACTIVE


    [ PARAMETERS ]
    i) hispeed_freq - Hi speed to bump to from lo speed when load burst. (Default value is scaling max freq)

    ii) go_hispeed_load
    - Go to hi speed when CPU load at or above this value. (Similar to Up-Threshold in other governors)

    iii) min_sample_time
    - The minimum amount of time to spend at a frequency before we can ramp down. (Sounds like Lazy governor?!)

    iv) timer_rate
    - The sample rate of the timer used to increase frequency.

    [ SAMPLE TWEAKS ]
    i) For battery:- [Interactive and battery?!! I'm capping the highspeed_freq in the hope of saving battery]
    Code:

    echo "95" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_loadecho "1000000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freqecho "10000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_timeecho "40000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
    ii) For performance:- [Assuming your scaling_max_freq is equal to or above 1400 mhz)
    Code:

    echo "80" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_loadecho "1400000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freqecho "40000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_timeecho "20000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate



    TWEAK ORNEGI:



    #!/sbin/busybox sh#No of values echoed to freq table and uvmv table should match the no of steps in your kernelecho "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_tableecho "1425 1325 1275 1175 1075 975 950 950"> /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_tableecho "200" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freqecho "1200" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freqecho "ondemandx" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



Sayfa 1 Toplam 4 Sayfadan 123 ... Sonuncu

Yetkileriniz

  • Konu Acma Yetkiniz Yok
  • Cevap Yazma Yetkiniz Yok
  • Eklenti Yükleme Yetkiniz Yok
  • Mesajınızı Değiştirme Yetkiniz Yok
  •  

Giriş

Facebook Baglan Giriş