Baterija - vodič, prva pomoć i savjeti

[yager]

Ultimativni vodič za bateriju

Baterija je postala jedan od (naj)bitnijih faktora na našim uređajima i nikad je nije dosta. Ako nešto ne valja s njom, smak svijeta se događa. Ovo je neki kratki vodič gdje je sastavljeno kako pospješiti autonomiju i potrošnju baterije.

Tema je namijenjena raspravi, pomoći, dijeljenju savjeta i screenshota vaših baterija.

Savjeti kako pospješiti vijek baterije

Lokacija

Jedna od prvih stvari koje će vas uređaj pitati kada postavljate svoj telefon. Većina korisnika ih dozvoli i kasnije zaboravi na njih. Lokacija i njezini servisi su jedni od većih potrošača baterije i u taj čas ju mogu iscjediti.

Stvar je u tome što ih ne morate uvijek imati upaljene već ih možete paliti po potrebi. Osobno ih imam uvijek isključene i uključim ih samo kada su mi potrebne

Wi-Fi

Skeniranje wi-fi mreža također utječe na bateriju. Ako neko dogledno vrijeme ne planirate koristiti wi-fi mrežu, ugasite wi-fi kako uređaj ne bi konstantno skenirao mreže i time utjecao na bateriju.
Možete također editiri build.prop dokument kako bi reducirali vrijeme skeniranja (potrebne su root ovlasti za to).
Editirajte wifi.supplicant_scan_interval. Početna vrijednsot je 180. Podesite ju na više kako bi reducirali vrijeme skeniranja.

Jačina signala / Način rada mreže

Jačina signala je uvijek problematična za bateriju. Slab signal će više utjecati na potrošnju baterije. Uz njega, konstantno mijenjanje između 3G/4G i 2G načina rada mreže će trošiti bateriju više.
Ovome možete doskočiti da podesite uređaj da koristi samo 2G, 3G ili 4G.

Primjer: osobno kada ne koristim baš uređaj, ili je on spojen na wi-fi, mrežu prebacim na 2G jer mi tada nije potreban 3G ili 4G.
Kada mi zatreba samo jednostavno putem togglea uključim 3G/4G.

Svjetlina zaslona

Zaslon je uvijek ubitačna stavka za bateriju. Ovdje nema puno pomoći. Što veći kontrast (svjetlina) to više utječe na bateriju.

Osobno mi svjetlina nikad nije na automatski već ju ručno podešavan. U zatvorenim prostorima koristima u prosjeku svjetlinu od 0-30%, dok na otvorenome koristim 30-65%, ovisno o vremenu.

Bluetooth / NFC

Bluetooth i NFC su dvije stavke koje se u većini slučajeva jako rijetko koriste a znatno utječu na potrošnju baterije. Ukoliko vam nisu potrebne, a rijetkima su potrebne, ugasite i palite ih samo po potrebi.

Sinkronizacija / Airplane mode / Animacije / Task Killers

Sinkronizacija: što se više sinkroniziranja odvija na uređaju to utječe više na bateriju. Na vašem uređaju vjerojatno ne trebate sinkronizaciju svih vaših računa u raznim aplikacijama ili automatski sinkronizaciju aplikacija. Podesite samo one potrebne da se automatski sinkroniziraju. One nepotrebne postavite na ručnu sinkronizaciju.

Airplane mode: koristite ga kada ne trebate mobitel na dulji period, tokom noći. Osobno mi uređaj ne treba tokom noći i uvijek upalim zrakoplovni način rada.

Animacije: animacije također utječu na bateriju i što ih je više to više utječu. Osobno ih sve isključim gdje god je moguće. A time dobijem i na brzini korištenja uređaja. Animacije možete podešavati pod Postavke-Opcije programera

Task Killers: task killers i sve slične aplikacije su stvari koje vam ne trebaju na uređaju. Ukratko, oni naprave više štete nego koristi.

Bloatware

Bloatware su sve one aplikacije koje dođu već instalirane na uređaju i koje vam ne trebaju a one rade u pozadine i samo utječu na bateriju. Veliki dio njih možete zamrznuti u postavkama (Postavke-aplikacije). Ako se dvoumite oko koje slobodno pitajte.
Naime, da bi mogli zamrznuti potpune sve potreban je root jer neke nećete uspjeti zamrznuti.

Kako pratiti potrošnju baterije

GSam Battery Monitor

Ovo je jedna od boljih aplikacija za praćenje potrošnje. Nažalost, na Lollipopu (čak i na Kitkatu) bez root ovlasti neće davati mnoštvo informacija no s root ovlastima postaje veliki izvor informacija o bateriji.
Play store link

Wakelock detector

Wakelocksi su jedna od bolnijih točaka. U principu to su aplikacije/servisi koji rade ili se pale kada je uređaj u stand byu. Ova aplikacija vam omogućuje uvid u to. Da bi ju koristili potrebne su vam root ovlasti.
Play store link

Disable service

Ako koristite Wakelock detector potrebna će vam biti i ova aplikacija. Pomoću nje možete blokirati pojedini servise unutar samih aplikacija. Također je potreban root.
Play store link

Greenify

Greenify nije aplikacija koja mjeri potrošnju, već ona pokušava produljiti vijek baterije. Greenify stavlja sve odabrane aplikacije u hibernaciju kada ne koristite uređaj ili kada to zatražite.
Osobno ju ne koristim no mnogi javljaju bolje rezultate s njom.
Play store link

Xposed Amplify Battery Extender

Ukoliko koristite Xposed framework možete staviti ovaj modul kako bi stekli kontrolu nad baterijom.
Play store link

[yager]

Za sljedeće stvari su potrebne ROOT ovlasti i custom recovery.

ROMovi

Romovi uvijek utječu pozitivno na bateriju i o njima nije potrebno mnogo priče.

Kernel

Kerneli su slični romovima jer se možete igrati s njima. Postavke unutar samoga kernela mogu utjecati značajno na bateriju.
Kernelom možete upravljati pomoću Trikcster MOD Kernel Settings aplikacije.

Undervoltanje

Undervoltanje je smanjenje voltaže pri radu procesora. Moguće je odredite koliko će koja frekvencija imati. Osobno koristim uvijek -50 vrijednost.
Kada se igrati s ovom postavkom prilikom mijenjanja nemojte odmah staviti kvačicu na "Set on Boot" jer ako je voltaža premala možete završiti u bootloopu i morati ćete flashati ispočetka.

Underclockanje

Underclockanje je mijenjanje takta procesora. Što manji takt, to bolja baterija. No, tada možete izgubiti performanse te je s toga potrebno pronaći zlatnu sredinu. Zlatna sredina je pronalazak takta gdje uređaj radi kao na najvišem taktu a opet pozitivno utječe na bateriju.

Governori

Governor u Android svijetu kontolira način na koji procesor podiže i spušta frekvencije prema zahtjevima korisnika. Oni ima važan utjecaj jer utječu na sami rad uređaja, fluidnost te bateriju.

Popis i objašnjenja najpopularnije governora možete pronaći skrivene ispod Spoiler taga. Opise nisam prevodio za sada. Ako će trebate prevedem ih kasnije.

Prikaži

I) MANUAL:

These are the 19 governors we're talking about.

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
20) Wheatley
21) Smartmax


1) Ondemand:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.

2) Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.

3) Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.

4) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.

5) Interactivex:
This is an Interactive governor with a wake profile. More battery friendly than interactive.

6) Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
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.

[yager]

Nastavak Governora:

Prikaži

7) Lulzactiveq:
Lulzactiveq is a modified lulzactive governor authored by XDA member robertobsc and is adapted in Siyah kernel for GS2 and GS3. Lulzactiveq aims to optimize the second version of luzactive from Tegrak by a) providing an extra parameter (dec_cpu_load) to make scaling down more sensible, and b) incorporating hotplug logic to the governor. Luzactiveq is the first ever interactive based governor with hotplugging logic inbuilt (atleast the first of its kind for the exynos platform). When CPU comes out of idle loop and it's time to make a scaling decision, if load >= inc_cpu_load CPU is scaled up (like original luzactiveq) and if load <dec_cpu_load, CPU is scaled down. This possibly eliminates the strict single cut-off frequency for luzactiveq to make CPU scaling decisions. Also, stand hotplug logic runs as a separate thread with the governor so that external hotplugging logic is not required to control hotplug in and out (turn On and Off) CPU cores in multi core devices like GS2 or GS3. Only a multi core aware governor makes real sense on muti-core devices. Lulzactiveq and pegasusq aims to do that.

8) Smartass:
Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.

9) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.

10) Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors )
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.

11) Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.

12) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.

13) Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.

To 'experience' Lionheart using conservative, try these tweaks:
sampling_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
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.

15) Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery.

16) SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.

17) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.

18) Powersave:
Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).

19) Performance:
Sets min frequency as max frequency. Use this while benchmarking!

20) Wheatley
Building on the classic 'ondemand' governor is implemented Wheatley governor. The governor has two additional parameters:

target_residency - The minimum average residency in µs which is considered acceptable for a proper efficient usage of the C4 state. Default is 10000 = 10ms.

allowed_misses - The number sampling intervals in a row the average residency is allowed to be lower than target_residency before the governor reduces the frequency. This ensures that the governor is not too aggressive in scaling down the frequency and reduces it just because some background process was temporarily causing a larger number of wakeups. The default is 5.
Wheatley works as planned and does not hinder the proper C4 usage for task where the C4 can be used properly .
For internet browsing the time spend in C4 has increased by 10% points and the average residency has increased by about 1ms. I guess these differences are mostly due to the different browsing behaviour (I spend the last time more multi-tabbing). But at least we can say that Wheatley does not interfere with the proper use of the C4 state during 'light' tasks. For music playback with screen off the time spend in C4 is practically unchanged, however the average residency is reduced from around 30ms to around 18ms, but this is still more than acceptable.

So the results show that Wheatley works as intended and ensures that the C4 state is used whenever the task allows a proper efficient usage of the C4 state. For more demanding tasks which cause a large number of wakeups and prevent the efficient usage of the C4 state, the governor resorts to the next best power saving mechanism and scales down the frequency. So with the new highly-flexible Wheatley governor one can have the best of both worlds.

21) Smartmax
Its no benchmark or ultimate perfromance governor, its a proper balanced ondemand.

The basic idea - which comes from smartass - is the concept of an "ideal" frequency.

The following strategy is used:
1) If load is above upper-threshold and current frequency is below ideal freq
-> jump to ideal in one step
2) If load is above upper-threshold and current frequency is at or above ideal freq
->do "ramp up" steps which will include all frequencies for a specific
amount of time - so compared to ondemand no "jumping" to max frequency
3) if load is below lower-threshold and current frequency is below ideal freq
->do "ramp down" steps
4) if load is below lower-threshold and current frequency is above ideal freq
-> jump down to ideal in one step

All those thresholds ramp steps and frequency stepping times are
fully configurable using sysfs. By default I tried to create a good balance.

The ideal frequency for "us" is 475000 which is the maximal frequency
of the LP mode of the tegra chip. This will allow using LP mode as much as possible

Additional to make it "snappy" smartmax has "touch poke"
So input events from the touchscreen will boost the cpu for a specific
time to a specific frequency.[/INDENT]

[yager]

Schedulers

Schedulers u principu utječu na responzivnost memorije i sustava, grupiraju procese prema prioritetima i paze da se određeni zadatak izvrši.

Objašnjena su također ispod spoiler taga i nisu prevedena. Ako će trebati prevedem.

Prikaži

1) Noop

Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.

Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.

2) Deadline

Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.

Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.

3) CFQ

Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.

Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.

4) BFQ

Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.

Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.

5) SIO

Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.

Advantages:
Simple, so reliable.
Minimized starvation of requests.
Disadvantages:
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.

6) V(R)

Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.

Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
I/O Schedulers


Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.

7) Anticipatory

Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.

So anticipatory prioritize read operations over write. It anticipates synchronous read operations.

Advantages:
Read requests from processes are never starved.
As good as noop for read-performance on flash drives.
Disadvantages:
'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.

Dijelite savjete, slike i ostale.
Ili pitajte za pomoć ako trebate.

[akoj]

Možda možeš nadodati isklučivanje NFC-a i Bluetootha. Znam hrpu ljudi kojima je oboje nonstop upaljeno, a da uopće ne koriste.
Inače -

[domy_os]

Odlična tema, konačno da sve imamo na jednom mjestu. Kako sam do sad promijenio više Android uređaja, svaki je imao neki problem s baterijom pa ću dodati još svoja zapažanja.



Kad su u pitanju sistemske stvari, dodao bih sljedeće:

1. Za one koji u postavkama nemaju developer options, potrebno je otići u settings > about phone i 7-8 puta stisnuti build number kako bi se ta opcija otključala.

2. Kod nekih ROM-ova unutar developer optionsa postoji i engineer mode, a kod nekih se isti poziva kombinacijama:

*#35789#*
*#*#35789#*#*
*#3646633#*
*#*#3646633#*#*

U engineer modu svakako preporučam isključiti fast dormancy opciju koja će ukratko usporiti prebacivanje između 2G i 3G i time na nekim modelima dosta smanjiti potrošnju baterije. Oni koji nemaju engineer mode, to modu napraviti preko third party aplikacija.

3. Oni koji ih imaju, neka svakako isključe opcije screen gestures, leather pattern i pocket mode, ako se iste rijetko ili nikako ne koriste. One drži touch screen i proximity senzor non-stop aktivnim i bezveze troše bateriju.

4. Neki modeli imaju problema sa senzorima pa je iste nakon instalacije ROM-a ili wipea potrebno kalibrirati jer "zaglave" na nekoj vrijednosti i također nepotrebno troše bateriju.

5. Tko nije zaljubljenik u live wallpapere, najbolje neka ih uopće ne koristi jer konstantno troše CPU resurse i usporavaju cijeli OS.

6. Kad se na SD kartici (nebitno interna ili externa) nakupi dosta smeća, mobitel više toga mora skenirati pa i kamera/galerija znaju opteretiti sustav. Tu pomaže čišćenje nepotrebnih stvari, brisanje odnosno obnavljanje thumbnail cachea i stavljanje praznih .nomedia fileova tamo gdje imate multimedijalni sadržaj koji ne bi trebao biti vidljiv OS-u odnosno galeriji.

7. Ako previše petljate po OS-u i ako mu dosta aplikacija pristupa s root pravima, to je potrebno smanjiti na najmanji mogući broj. Vjerujem da svi imaju aplikacije koje stalno imaju root pristup, a zapravo im to treba samo povremeno.

8. Ako ne putujete često izvan države i pogotovo ako boravite blizu granice, svakako ručno odaberite mobilnog operatera. Time ćete spriječiti automatsko prebacivanje među mrežama i uštedjeti na računu za mobitel jer neće ići automatski u roaming.



Kod Google bloatwarea pripaziti na ovo:

1. Google Play Store prilikom updatea zna napraviti cirkus i također "cuclati" bateriju pa je tu i tamo potrebno obrisati data nakon čega se stvar ponovno stabilizira.

2. Google već neko vrijeme ima problema s lociranjem pa umjesto GPS high accuracy opcije stavite device only. Kod nekih mobitela ta postavka nije trajna pa ju je potrebno ponovno namjestiti nakon svakog uključivanja GPS-a.

3. Slično kao i s Play Storeom, problema može biti i s Google Keyboardom pa je potrebno provjeriti opcije ili preći na alternativno rješenje.

4. Još jedna Googleova glupost je Google Search i Google Now. Preporučio bih da to svakako isključite odnosno deinstalirate, a ako ga već morate koristiti, onda barem isključite opciju "Ok Google".



I na kraju, određeni modeli s MediaTek chipsetom imaju bug u kernelu pa se u određenim uvjetima zablesira CPU governor i procesor ne ide u deep sleep nego ostane na nekoj većoj frekvenciji tipa 700 MHz, 1 GHz i slično. Na Prestigiu mi se to pojavljivalo čim bi baterija pala na 15% i aktivirala se LED-ica za low battery. Rješenje je bilo napuniti bateriju preko 15% i resetirati mobitel. Kad sam to skužio, više joj nisam dao da padne na 15%.

Toliko zasad od mene. Ako se još nečega sjetim, napisat ću.

[yager]

Thanks na nadopunama.
Dodati ću te stvari u gornje postove također.
Drago mi je da se skupljaju savjeti polako.

[xlr]

Većina stvari je pokrivena u prethodnim postovima pa ću samo spomenuti što osobno radim kod štednje baterije i ubijanja wakelockova. Danas mogu komotno reći da sam riješio sve probleme sa glupim wakelockovima bez da sam telefon pretvorio u dummyphone ili napravio neke kompromise.

Wifi scanning always available:
Ugasiti ovu opciju u settings - wifi - advanced. Ne treba vam to u životu.
Opcionalno: fiksirati wifi frequency band na 2,4 ili 5 GHz. Osobno ne koristim 5GHz mreže pa selektiram samo 2,4.

IPv6 (root i custom kernel):
Još na SGS2 sam imao problema s wlan_rx_wake wakelockovima i to sam riješio gašenjem IPv6 podrške za wifi. Potrebno je editirati jedan flag u /proc (mislim da treba custom kernel za ovo). Flag se resetira nakon reboota ili reconnecta. Potrebno ga je automatski aktivirati preko init.d skripte (traži podršku rom-a) ili neke aplikacije tipa Tasker. U Taskeru imam profil da svaki put kada se mob spoji na neku wifi mrežu dogodi se sljedeće:

echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6

Google location reporting:
Ovo je valjda najgora stvar za bateriju i prvi korak za poboljšanja. Ako vam ne treba ova usluga odite u settings - location - google location reporting i ugasite location reporting i location history. Ovo rješava raznorazne nlp wakelockove, ne sjećam se više točno koje.

Disable location services (root i custom rom?):
Ako ste fan high accuracy načina pozicioniranja onda želite ubiti pozadinske wifi/cell lokacijske procese kada vam mob spava. Potreban je root, Tasker i Secure Settings app. U Taskeru sam napravio profil da kada mi je ugašen ekran ugase se i "location services". To nije GPS! GPS normalno radi u pozadini ako ga koristite, ali koliko sam skužio to ubija ono wifi lociranje ili nešto tome slično.

GPS nije battery sucker ako ga ne koristite! Više suckaju glupi i konstantni location requestovi od strane Googleta jer to ne možete kontrolirati (Google Play services, Google now i sl.).

2G/3G switch:
Tasker automatski prebacuje mrežu na 2G kada sam spojen na wifi. Moguće podesiti da se prebacuje na 2G kada je baterija slaba, kada je ugašen ekran itd. Varijante su šarolike.

AppOps ili PrivacyGuard (custom rom):
Opcionalno ovo možete naći u custom romovima i služi tome da pojedinim aplikacijama kontrolirate permissione. Tako npr aplikacijama možete zabraniti čitanje lokacije, čitanje kontakata i sl. ako mislite da to neće poremetiti rad same aplikacije.
Ovdje najčešće gasim "keep awake" dozvolu za pojedine appove koji koriste tu opciju, ali meni to ne treba. Ponegdje ugasim i "location", ali nije potrebno ako već imate sređene lokacijske usluge na razini roma.




Par aplikacija koje koristim...

Per-App Modes:
Omogućava izradu profila prema aplikacijama. U profilima podešavate kernel postavke tipa CPU takt, GPU takt, i sve ostale "flagove" (Kernel tunables) koje možete ručno dodati ovisno o podršci custom kernela kojeg koristite. Ova aplikacija ima mogućnosti TricksterMODa (ili bilo kojeg drugog kernel tune appa), ali za svaku aplikaciju zasebno. Zašto bi cijeli mob underclockali/overclockali kada to možete podesiti za pojedine appove

DisableServices:
Najkraće rećeno - ubiti sva Googleova sranja koja vam ne trebaju. Osobno ubijam sve od dolje navedenog a odnosi se samo na Google play services:
- sve što u svom full opisu (ne short!) ima riječi "fitness", "wear", "cast" ili "cast_mirroring" (ne broadcast!). To su stvari vezane za Google Fit, Google Wear (satove) i Android Cast.
- ako imate brdo GMS wakelockova onda gasite "ConfigFetchService" (ne ConfigService!) i "UserPresenceService"
Ima tu još nekoliko tih servisa koje sam probao ubijati, ali nisam dovoljno testirao.

ElementalX kernel app:
U kombinaciji s istoimenim kernelom na Kitkatu imam power save mod kada baterija padne na 15%. Slično kao na Lollipopu battery saver. Inače sam zaglavio na tom kernelu pa mi taj app dobro dođe. Pored njega preporučam i KControl (primarno za bricked kernele) i već spomenuti univerzalni Trickster MOD.

---------- Post added at 14:07 ---------- Previous post was at 14:04 ----------

Thanks na nadopunama.
Dodati ću te stvari u gornje postove također.
Drago mi je da se skupljaju savjeti polako.

Kao ultimativni dodatak štednji baterije možeš navesti i gašenje haptic feedbacka kod tipkanja, a konkretno za one IM ovisnike. Mislim da to ima smisla iako nisam osobno testirao.

[yager]

Iks se raspisao pošteno.

Što se tiče haptic feedbacka, ne utječe na bateriju baš. Osobno ga koristim uvijek. Probao sam bez njega i nema razlike pa ga s toga nisam ni stavio.

[xlr]

Spomenuo sam ga najvise iz razloga jer recimo elementalx power save mod i lollipop battery saver gase vibru. Meni osobno power save zna pristojno izdrzati sa zadnjih 15% ali budem probao prezivjeti dan bez vibre pa cu/cemo biti pametniji dosta tipkam pa ne bi trebao biti problem testirati. Povukao si me s ovom temom da se raspisem jer jednom sam ti spominjao da sam nesto slicno mislio natipkati u N5 temi samo sam bio lijen.

[yager]

Bolje da tu tipkaš mudre savjete nego po whatsappu
Ajd isprobaj to za haptic pa vidi. Ja nisam skužio razliku na Nexusu a ni na LGu sad.

I fali ti 6 još samo u kolekciji (4,5,7)

[Moby]

Znači, jel pametnije isključiti automatsko podešavanje svjetline ekrana ili ga ostaviti uz npr. 30% max osvjetljenja?
Automatska rotacija?
Meni piše da mo GO weather troši do 30%, widget naravno.

[yager]

Za bateriju bolje je ugasiti automatsko podeševanje jer čim je uključeno i sensor za svjetlo je aktivan stalno onda.
Što se tiče rotacije ona ne utječe nešto predrastično. Osobno mi je uvijek isključena jer me živcira kad se slučajno zarotira ekran ako mob dođe u neki čudniji položaj.

Što se tiče GO weathera, posve logično i normalno za njega kad koristiš jedan od gorih kompleta koji postoje na marketu (tu mislim na cijeli asortiman GO aplikacija). Preporučam da zamijeniš s nekim drugim (pogledati teme za aplikacije).

[xlr]

I fali ti 6 još samo u kolekciji (4,5,7)

Ako ćemo biti picajzle onda bi se trebao ponoviti i sa 7icom 2nd gen :zubo:
/off

[water]

Prije svega, pozdrav svima. Stvarno pišete korisne stvari i puno toga zanimljivog se može nać.
O aplikacijama i sve ostalome je puno toga napisano, a drago mi je da ima i ovaj dio o baterijama jer kad se sve zbroji i oduzme, sve o procesorima, ramovima, romovima i aplikacijama ne bi bilo moguće bez baterije
Imam jedan problem pa ako neko može pomoći:
Imam skroz novi, odličan, android mobitel, nije rootan, baterija li-po 2150. Tvornički je bio na jelly beanu i prije par dana sam ga prebacio na kitkat. Kitkat radi super, ali je problem baterija koja se doslovno duplo ili troduplo brže prazni nego na jelly beanu koji je bio do tad. Sve ove stvari sam već prije pogasio o kojima govorite tu, ali opet slabo. Npr tokom noći sa ugašenim zaslonom, wifijem i mobile data se isprazni po 10, 15 posto. A tokom dana, osim šta prazni bateriju poprilično brzo, nekad se zamrzne na npr 67% i tako stoji sat vremena, a onda u sekundi padne na npr 51%.
Stvarno neznam šta više napravit, zanima me jel znate možda nešto o kalibraciji baterije, nekoj dobroj aplikaciji za to i kako se to uopće radi, ili možda neko treće rješenje?

Hvala na odgovorima i pozdrav

[imart]

niti si napisao koji je mobitel, ni koja verzija jellybeana, jel službeni ota update na kitkat ili si ručno radio?
premalo detalja si dao..

[water]

Kitkat je 4.4.2 i upgrade je napravljen kako treba, zadnja verzija, čim su službeno ponudili da se upgradea....
da opet ne kompiliciramo puno, zanima me jel neko zna neki dobar program ili neku dobru aplikaciju s kojom se može napraviti dobra kalibracija baterije. Android google app store je pre pre zasićen sa raznoraznim takvim aplikacijama pa me zanima jel neko zna konkretno neku aplikaciju s kojom se to može kvalitetno odraditi??
Ponavljam još jedan put ako je to bitno: mobitel nije rootan.
Ps, može prijedlog i neke koja se možda plaća. Ne mislim plaćati, ali se možda može naći na blackmartu i sl.
Pozdrav

[xlr]

A zasto zelis kalibrirati bateriju kad je ona tvornicki kalibrirana? Radije reci koji je mob da imamo polaznu tocku. Najbolje sto mozes kao nerootani korisnik napraviti je factoty reset i test baterije bez ikakvih instaliranih appova. To bi ja napravio u tvom slucaju jer problem mozda moze biti i hardverske prirode.

[imart]

Nikakva aplikacija ti nece pomoci oko baterije u tom smislu i opet nisi napisao koji je mob..

[water]

pozdrav,
mobitel je asus padfone 2,
jednostavno kao sto sam gore napisao, nakon updatea, baterija se pocela cudno ponasati, uz sve ovo gore nabrojano, jos i npr, u sekundi joj padne postotak za 10 posto, i da ne govorim kako krace traje sve skupa.
ne vidim drugi razlog osim da se nesto poremetilo kod prijelaza sa JB na KK.
Zato mislim da je jedino možda moguće nešto malo ispraviti sa nekom ok aplikacijom ako bi uopće i to nešto pomoglo. pa možda ako znaš neku ili ako si koristio već za kalibraciju, jer na tim android play storovima ima i ogromna hrpa smeća i teško je ubosti nešto da baš radi.

[imart]

Probaj uc u recovery i napraviti hard reset. Ne znam kak se na asusu ulazi u njega malo progooglaj.

[water]

Ne bi radio hard reset, ni stavljao na tvornicke postavke jer mi je vec bio nedavno na tvorničkim postavkama i nije ništa pomoglo.
Zanima me jel se zna za neku ok aplikaciju za kalibraciju baterije od ovim miljon na storeu, da je isprobana i da radi. Ako niko nezna sam ću pokušat nać.
I možda nešto za gašenje wakelock aplikacija za ne rootani mobitel.

[xlr]

Ali app za kalibraciju baterije ne postoji Ima ih miljon jer je to, pored battery saver i task killer appova, nesto za cim ljudi sline. Probaj bilo koju, onu s najboljom ocjenom, s najvise downloada... Siguran sam da sve rade dobro svoj "posao".

[water]

aj dobro probacemo nešto bar za početak od tih battery doctora, juice defendera i sl, možda šta i ispravi
jel znaš možda i neku aplikaciju koja radi za gašenje ili hiberniranje wakelock aplikacija. Vidim da si već i pisao o tome, ali je problem što mobitel nije rootan i automatski je sužen svaki izbor.
i isto tako ako možda znaš, ili neko drugo, jel se mogu kako maknit ovi googlovi play, kiosk i movies. Ako ih se već ne može izbrisat bilo bi poželjno da ih se skroz makne i stave u neku hibernaciju, ili ako ne može ni to, da ih se bar nekako sakrije da ne stvaraju gužvu među aplikacijama jer samo smetaju.

[polist]

aj dobro probacemo nešto bar za početak od tih battery doctora, juice defendera i sl, možda šta i ispravi
jel znaš možda i neku aplikaciju koja radi za gašenje ili hiberniranje wakelock aplikacija. Vidim da si već i pisao o tome, ali je problem što mobitel nije rootan i automatski je sužen svaki izbor.
i isto tako ako možda znaš, ili neko drugo, jel se mogu kako maknit ovi googlovi play, kiosk i movies. Ako ih se već ne može izbrisat bilo bi poželjno da ih se skroz makne i stave u neku hibernaciju, ili ako ne može ni to, da ih se bar nekako sakrije da ne stvaraju gužvu među aplikacijama jer samo smetaju.

Cini mi se kao da vec sve znas u vezi cega pises, ali testiras forumase
Ljudi se razumiju u mobitele i kazu da takve aplikacije ne pomazu, ali ako si uvjeren da postoji ta aplikacija koju trazis, isprobaj te battery savere pa ces se i sam uvjeriti.
Probaj greenify u vezi hibernacije aplikacija.
Mozes to maknuti u postavke->aplikacije i tamo odaberes sto zelis maknuti te stisnes onemoguci.