Salve ragazzi ho la V38 e il boeffla omnirom. Volevo dirvi che la batteria mi dura pochissimo ed ho notato che quando il telefono va in sospensione si accende una luce rossa fioca che rimane sempre accesa (penso sul sensore di prossimita). Può essere una causa della scarsa durata della batteria? Come posso risolvere? Grazie in anticipo
per togliere quella vai in Impostazioni>Temasek spare parts>Screen and animations>Lockscreen Notification>attiva Lockscreen notifications e deflaga tutto, poi disattiva di nuovo lockscreen notifications :)
30-01-14, 16:06
AlexVip
Quote:
Originariamente inviato da Al3xI98O
Nei miei vari test ci sono stati anche quelli senza kernel quindi senza nessun tipo di settaggio per il risparmio... (con la ROM in firma invece nessun problema nemmeno con i settaggio di risparmio (ma è stock-based quindi...).
Puoi provare cosi, se vieni da rom Samsung, full wipe, flash script di pulizi flash di cm 11 e tutta il resto della guida, di nuovo flash di pulizia prima e dopo il flash della temasek e poi flash del kernel Custom che desideri, installa l app dedicata del kernel manualmente senza usare titanium, e imposta i settaggi sempre manualmente, se ancora salta nn saprei che dire
30-01-14, 20:51
lalaspdn
Quote:
Originariamente inviato da Al3xI98O
Questa ROM eredita tutti i problemi della CM immagino, vero?
I due prblemi CM che NON sopporto più sono:
- battery drain osceno che non riesco a risolvere
- musica che "scatta" con il monitor spento
Forse c'è una interessante novità per il problema della musica che salta.
Alcuni utenti hanno risolto (!) aumentando da 200 a 300, o se non fosse sufficiente fino a 400, la frequenza minima della cpu.
Spero che l'info possa esserti di aiuto.
30-01-14, 23:14
Al3xI98O
Quote:
Originariamente inviato da lalaspdn
Forse c'è una interessante novità per il problema della musica che salta.
Alcuni utenti hanno risolto (!) aumentando da 200 a 300, o se non fosse sufficiente fino a 400, la frequenza minima della cpu.
Spero che l'info possa esserti di aiuto.
Interessante :) anche se in teoria... cmq quando tornerò a CM proverò :)
31-01-14, 08:31
criscla
Quote:
Originariamente inviato da lalaspdn
Forse c'è una interessante novità per il problema della musica che salta.
Alcuni utenti hanno risolto (!) aumentando da 200 a 300, o se non fosse sufficiente fino a 400, la frequenza minima della cpu.
Spero che l'info possa esserti di aiuto.
Questa è una bella dritta.Ho modificato a 300 e la musica è saltata solo due volte (prima mi saltava in ogni traccia ed ogni minuto).
C'è ancora da capire perchè il suono in certi giochi esce distorto.
Grazie ancora
31-01-14, 12:36
Egocentriko
ma come si imposta la frequenza minima? Uso il kernel Boeffla
31-01-14, 12:41
satoshi
Quote:
Originariamente inviato da Egocentriko
ma come si imposta la frequenza minima? Uso il kernel Boeffla
Il tuo kernel ha un tool per la gestione dei suoi parametri. Basta usare quello. ;)
Per reperirlo dai un'occhiata alla discussione del kernel (di solito in prima pagina).
31-01-14, 13:04
lalaspdn
Quote:
Originariamente inviato da Egocentriko
ma come si imposta la frequenza minima? Uso il kernel Boeffla
Come ti hanno correttamente suggerito, scarica l'app "Boeffla-Config V2"dallo store, e segui la discussione del kernel per i settaggi corretti.
31-01-14, 13:11
satoshi
Domanda veloce... Ho visto uno screen di un utente dove, oltre ai soliti mtp e ptp, si vedeva anche il spirò a ums nelle opzioni usb. Questo vuol dire che temasek ha ripristinato il supporto nella rom o è il boefla che lo ripristina? :)
03-02-14, 08:12
Il Burocrate
Build V42
i9300 - md5sum: 05c9cda8069a063137f122dd8af82042
CHANGELOG SINCE V41
Spoiler:
Add "OmniSwitch" by OmniROM
Add back quick unlock for pin/password security
Add updated "LocationTile" from SlimRom
- we already modified to use the basic 4.4 location mechanism. Still it was very basic. Now using the same attempt like in Settings to controll location mode (high accuracy, battery saving, device only) and on/off state
- longpress switches between the states. Normal click turns it on/off. Compared to settings turning on will recover last state where it was turned off. As well it respects the sharing location warning dialog either when you switch on into a mode which use it or you switch into a mode which uses it and it was not confimed.
- Slight corrections to original AOSP code to reflect the changes in LocationController even though this code is non operational
Add "Handle navbar heights correct on dpi changes + more" - SlimRom
Till now we set the height in px in the settings. Which is a problem
especially on multiDPI roms like we are when the user afterwards changes
the dpi due that it isn't calculated correct anymore on the new dpi.
This commit does
- save the dp value in provider and calculate the real px in fb
- clean up the settings stuff for it + do it a bit nicer (only settings part
where we do not set the value for the listview)
- as well this commit disables movable navbar for tablets (we may will enable
it in future but it needs a lot more work to have it on tablets correct working)
- add Converter class for common methods we always use....till now only px->dp
and dp->px method
Comments from Slim dev:-
just a small hint dirty flashers will have a huge navbar suddenly on bootup
(at least if you had before changed something on the navbar heights) :p
so reset it to default in settings with the reset button or clean install
one of both :D
Add "Updates to QuickSettings : Quick Collapse"
Add "Super advanced Custom Toggle" - SlimROM
Revert "LockScreen: allow long-press actions from hardware keys"
- Conflicts with SlimROM hardware key rebinding rendering this feature non-reponsive. Revert for now till I find a solution.
Revert "Email TRDS" - Till I sort out the color stuffs.
frameworks/base: server: Treat non-default route as host route
- When constructing ip route command in addRouteWithMetric, we used to check whether the given route is a host route. In some cases, the isHostRoute() check can return false for
non-default routes. To make this check more foolproof, check whether a route is non-default in order to treat it as a host route.
frameworks/base: Bluetooth: Fix to avoid framework reboot during monkey.
- A case where monkey is running & sometimes framework is disconnected due to unhandled java Exception during the unbinding of HID device service on unsuccessful unbinding. Handling java Illegal Argument exception while unbinding HID device service solves this issue.
frameworks/base: ProcessCpuTracker: Fix ArrayIndexOutofBoundsException in tempSpeeds
- If time_in_state file is not available mCpuSpeeds is created with size 0 and subsequent call if the file becomes available there is an ArrayIndexOutofBoundsException. This change avoids the crash by breaking out of the loop, also adds error logging
- CRs-Fixed: 553569
frameworks/base: Fix dest == src bugs in Matrix.cpp.
- The main bug was that the AutoJavaFloatArray autoSrc was not passing in read only. This meant that the destructor overwrote the data which the autoDst AutoJavaFloatArray had written in it's destructor.
This case only happened if src == dest and the arrays were copies. Also improved performance by passing in read only a few other places.
- Bug: 12570144
frameworks/base: [ActivityManager]: Fix the activity visibility state not sync between ActivityManager and WindowManager
frameworks/base: GpsLocationProvider: look for config file in /etc/gps.<ro.hardware.gps>.conf
- The property ro.hardware.gps can be specifid to allow a single system image to work with differrent GPS chips. The HAL layer will use it to load /system/lib/hw/gps.<ro.hardware.gps>.so. Add support to GpsLocationProvider to use the same property to find /etc/gps.<ro.hardware.gps>.conf, falling
back to /etc/gps.conf if the property is not set or the file is not present.
frameworks/base: fb: unbreak recents animations on thumbnail click or dismiss recents screen
- We load now correctly the recents screen and preload the first task on press down off any key to get always recents without issues up. We cancel only if any other key was pressed. I discovered during I am working on new recents that this solves all issues but has one downside that if he user dismiss he recents screen or click on one of the thumbnails to bring the choosen app to forground that of course the last thumbnail is not cleared. Due that the entry animation and some other things depent on what is currently preloaded we need to cancel first task to have always in all cases the right animation.
- Fix it with just calling cancelPreloadingFirstTask() if the user either clicked on one of the thumbnails or dismissed the recents screen.
frameworks/base: fix search textfield
frameworks/base: fix number picker blue line and highlight
frameworks/base: Fixed cancel() not working correctly …
- The method handleMessage(Message msg) from mHandler variable was not checking if the timer was cancelled, so sendMessageDelayed(obtainMessage(MSG), delay) was keeping the timer alive. The patch simply adds a boolean and checks if the CountDownTimer was cancelled before calling
sendMessageDelayed(obtainMessage(MSG), delay)
- bug: https://code.google.com/p/android/is...etail?id=58668
frameworks/base: Fix the issue that the top of fullscreen dialog is clipped away …
- The visibility of status bar comes from the top fullscreen window, not from the focused window.
That has to be taken into account during the calculation of the decor rect. You can use mTopIsFullscreen for this purpose.
Settings: Unbreak PIN/Password lockscreen options
Settings: Fix memory leak in ManageApplication ApplicationsAdapter new a Session member and make it has a reference to it self. If we don't release it explicitly, the cross reference will
cause memory leak.
Updated cm source - Quite a fair bit. Read on your own :p
