Sisi pensavo ci fosse un codice o un modo per visualizzarlo come per le sammy :P cmq ora che ci penso avevo installato la blackbox 1.3.1 con l'ultimo firmware ma per fortuna lo sviluppatore ha fatto in modo che la EFS e il modem non venisse toccato, anche perché sto passando da rom 4.1.2/ 4.2.2/ 4.3 senza nessun problema... Scusate l'OT. :banghead:
TEMASEK's CM 10.2 V36
Added CM Account
Frameworks: refactor, cleanup, centralize, fixes, features - SlimROM
- refactor a lot code
- remove duplicates and centralize
- a lot fixes and some features like diable navring, color mode for notification shortcuts
Use proper System Icon identifier for navring - SlimROM
Do not show up navring on home longpress on navbar - SlimROM
Fix possible QS NPE if navbar was not set - SlimROM
Frameworks: Fix navring keyguard + ehancementes for SlimAction in preparation - SlimROM
Frameworks: better navbar and navring support for ppl without gnow an installed without google now had some negative effect on our custom navring/navbar actions - SlimROM
- do not depend on search action on tiny circle lockcreen...check targets available instead
- same for navbar transparency
- fix google typo
- split ontouchlistener for home button and tiny circle due that it does not make sense to react same like home button if the user assigned to the home button a custom action
Frameworks: activate PIE on lockscreen apps - SlimROM
- currently the situation was that every application started on lockscreen had disabled pie (because lockscreen disables it). Downside on incoming call or camera widget the user did not have a navigation. As well on unsecure lockscreen the user could not navigate further
Fix possible NPE - SlimROM
- mTopFullscreenOpaqueWindowState is on certain conditions null and will throw an NPE....check for it to prevent it
Frameworks: activate PIE on Lockscreen - SlimROM
- completly activate it now if navbar is disabled, expanded desktop or whatever. The bottom trigger can be used on Lockscreen if the user want (left and right does not make sense due the widgets.
- If navigationbar hints are disabled it show instead
the home button the tinny circle which opens search/gnow. Longpress
action is the same like the one which was bind to the homebutton
- slight adjust of default values trigger height and overall size
- as well colorize and set alpha on navbar for the tinny keyguard circle like the other navbar buttons to be consistent
Framworks: clean up trigger code + small fix - SlimROM
- how to reproduce the bug
activate hide trigger on ime.....open ime...pull down notification drawer close it again.....pie trigger left and right do not change back again
Frameworks: do not call every time setupTriggers if pie is disabled - SlimROM
Fix: lockscreen bottom trigger on expanded desktop mode - SlimROM
- did not show up in expanded mode before. Only on navigation bar disabled
or 0 values
another cleanup (SlimPIE) - SlimROM
Frameworks/Settings: remove always transparency mode navbar/statusbar - SlimROM
Frameworks: simplify custom lockscreen background code - SlimROM
- remove observer for transparency and handle it better
- add multisuser handles
- smaller fixes and code cleanup
- simpfliy custom background handling and change to our needs (thanks Danish)
Improve scrolling cache
- Scrolling cache helps make short scrolls/flings smooth but will cause stutter when long flings are made. This patch disables scrolling cache when long flings are made.
- This patch also fixes a related bug where scrolling cache will not be enabled properly when transitioning from flinging to scrolling.
- Patch Set 2: Calculate threshold based on maximum velocity (Sang Tae Park)
- Credits: Pawit Pornkitprasan
NPE in SearchManager.triggerSearch
- mAssociatedPackage field is never initialized and cause NPE.
Fix to NullPointerException when activity is relaunched
- When ChooseTypeAndAccountActivity is relaunched and resumed by ActivityManager a call is made to onActivityResult without first triggering onResume. This leads to mAccounts object still being null.
- Fixed by properly setting mAccounts object if it is null prior to use after function onCreate has been called.
Fix for NullPointerException in HTML5VideoViewProxy
- There is a missing null check of mHTML5VideoView.
Frameworks - Forward compatibility fixes
Frameworks: bluetoothmanager avoid NPE - SlimROM
- callback on unregister get sometimes null. Not sure where it comes from currently due that all instances calling the unregisterStateChangeCallback are
well. Whatever to prevend the NPE check callback for null like stated in RemoteCallBackList.java
Missing break in switch statement
Fix appwidgets not updating
- Previously there was a bug where if an appwidget's update caused a
TransactionTooLargeException then the AppWidgetServiceImpl.Host's
callbacks were completely disabled, for all widgets.
- The fix still allows a DeadObjectException or other RemoteException to disable the host callbacks, as that would be caused by a bad host.
- Fixes issue 28216 on the public tracker https://code.google.com/p/android/is...etail?id=28216
Updated cm source
md5sum: ad3d9b704ef2fd0624a8d9c21df46358
Locaa92 (11-09-13)
Ecco... Questo è un changelog !!!
Cmq i giochi so' finiti....
Speriamo che Samsung fallisca e che Google/Motorola se ne escano con device all'altezza dei loro nomi !!!
__________________________________________________ ________________________________
Huawei Mate 10 Pro
Huawei Mediapad M5
Speriamo !!!
ma hai qualche info sulla data ?
Ultima modifica di anarky81; 11-09-13 alle 11:13
Usando questo provvisorio noti miglioramenti apprezzabili ?!?
Nell'uso quotidiano mi sembra di no ma l'ultima relase 36 insieme al kernel temasek (non quello stock CM con la ROM) danno già veramente degli ottimi risultati e onestamente il telefono ha adesso una usabilità, reattività e una fluidità tale che direi siamo al top delle caratteristiche.
sopra questo cio vogliono 2G di RAM e comunque gli S4 stock che vedo a giro non hanno veramente niente da invidiare
ho inserito una ZRAM da 200M con uno swappiness 60% che sta girando senza problemi (potrei provare ad aumentare lo swappiness per forzare l'uso della ZRAM ma visto che non è tutto testato al 100%, vorrei mai che succede qualche disastro)
dimenticavo la 36 con l'uso dell' ultimo governor pegasusq mi sembra invece che abbia migliorato ancora i consumi