[ROM][CM11][4.4.2]temasek's UNOFFICIAL all build r3p2MALI(I9300)

[anarky81]

La V36 ancora non l'ho flashata...
Però ieri ho notato che con la V35 giocando a RealRacing 3 il device scalda tantissimo !!!

Dopo 2/3 gare devo uscire perché ho paura di bruciare qualcosa... Voi notate nulla del genere ?!?

Stefano

[Locaa92]

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

Io stranamente con la v35 e kernel temaseak boeffla NOABB sto avendo un sacco di wake lock da parte dei servizi Google e dal sistema operativo... Ho fatto i Wipe ma non si è risolto, stasera provo a vedere se installando la v36 qualcosa cambia. Quale kernel temaseak usi? Governor pasasqu, I/O sio? Per la gestione del kernel usi il programma integrato con la CM?

[almaximo]

Io stranamente con la v35 e kernel temaseak boeffla NOABB sto avendo un sacco di wake lock da parte dei servizi Google e dal sistema operativo... Ho fatto i Wipe ma non si è risolto, stasera provo a vedere se installando la v36 qualcosa cambia. Quale kernel temaseak usi? Governor pasasqu, I/O sio? Per la gestione del kernel usi il programma integrato con la CM?

I wakelock dei servizi nlp di google sono un male di tutte le ROM 4.3 e non sono legati alle modo ma all'implementazione di google now. Se non ti interessa la geoloccalizzazione disabilita tutto dalle impostazioni google e vedrai come migliora il drain della batteria. Governor pegasusq senza toccare altro stweaks per la gestione ultima versione disponibile. Per l'audio quelli che ti piace di più. Tassativo noabb

[anarky81]

Quindi mi dici di mettere la V36 con "080913-2023-cm10.2-i9300-linux3095-WOLFSON-NOABB-temasek.zip "...

Stasera provo... hi hi hi

[almaximo]

La V36 ancora non l'ho flashata...
Però ieri ho notato che con la V35 giocando a RealRacing 3 il device scalda tantissimo !!!

Dopo 2/3 gare devo uscire perché ho paura di bruciare qualcosa... Voi notate nulla del genere ?!?

Stefano

Potrebbero anche essere i driver non nativi. Appena rilasceranno la prima 4.3 ufficiale dovrebbe andare a posto

[almaximo]

TEMASEK's CM 10.2 V37

smdk4412: add netflix hack - rmcc
- https://github.com/temasek/android_d...f314932b01c1fa

LCD density backup - SlimROM
- https://github.com/temasek/android_v...2b92e963620619

Frameworks/Settings: rework navbar and statusbar transparency/color handling - SlimROM
- All current implemented versions of nav and statusbar transparency which are around are not really perfect and all have downsides. After I saw the implementation from Romanb (thanks) I got an idea to solve especially the problem on keyguard without forcing the user to set for keyguard seperatly a transparency to have a good result. Main problem is that aosp does not allow to overlay the navbar with a shadow.

This commit does:

- introduce central TransparencyManager (thanks Roman)
- introduce a layerDrawable with a ColorDrawable as overlay and underlay
to get consistent results on keyguard to show the shadow
- introduce a overlay to animate the navbar shadow like the PIE background shadow
when the user is not in expanded mode. So the user get the whole screen darken (or colored).
- get complete rid of backgroundalphadrawable class
- allow colorize of theme (theme engine) navbar/status bar background changes
reset to default shows as usual the theme without manipulation
- expand the custom background area on lockscreen behind the statusbar
(navbar AOSP does not allow)

- default wallpaper and full transparent mode is now completly consistent and nice
looking on every possible setting.
- full color lockscreen reflects the color now behind the navbar
to imitate same behaviour like the default wallpaper on lockscreen. As well
now consistent and nice looking on every possible setting.
- lockscreen background image mode is the only one where a 100% consistent solution
is not possible due that the image is always smaller on lockscreen (not expandable behind
navbar) and I do not see a good way to put in the underlay a partly image in a nice way
...to avoid weird transparency draws the transparency on navbar
is set to the chosen lockscreen background transparency as long the lockscreen transparency
is smaller then the navbar/statusbar transparency. Todo: notify in settings the user about
the behaviour change so that it is no surprise.
- add multiuser compatibility to serveral vars
- margin fix on lockscreen
- hide statusbar on lockscreen on expanded or autohide statusbar mode
- add option to unlink colorizing on apps
- optimizing and a memory leak fix
- cleanup

Frameworks: move complete keyevents into SlimActions - SlimRom
- still to lazy to doe the HW key rebinding revamp but we need this move as well for that and it is from codeview much cleaner

This commit does:
- move all key event actions into SlimActions
- get rid off ExtensableKeyViewButton class and handle all over
the AOSP KeyViewButton class which is now reverted nearly to the aosp
one with slight modifications for the key handling
- fix the double vibrations on home, back and recents
- fix double sound on menu action on PIE and navbar permanent menu buttons
due that the click sound is played by PhoneWindow.java for ActionBar events
we do not play our sound for this action
- cleanup a lot unused imports

Frameworks: add Accessibility events to navbar, pie and navring for click and longpress actions - SlimROM

Frameworks/Settings: add expanded desktop to SlimActions - SlimROM

Frameworks/Settings: add power menu to SlimActions - SlimROM
- like the feature before we can see now how easy the util class and the dlsv is for us to use....just 8 lines + drawables and we have a new feature available on all navigations

Frameworks/Settings: add torch to SlimActions - SlimROM

Frameworks: add DeviceSupportUtils helper class - SlimROM
- adapted partly from cm (thanks) + own modification for our needs. Currently unused but there will follow a bunch of commits which will use it next days

Frameworks: add filter method for supported phone features which will be later used for any settings arrays which need to be filtered out. - SlimROM

Frameworks: fix default transparency value - SlimROM

Frameworks: fix typo in ic_action_power_menu.xml - SlimROM

Prevent nullPointerException by updateBondedBluetoothDevices
- In some very rare cases difficult to identify, it seems that the IBluetooth.getBondedDevices() returns a Set with a null element.
- This patch will prevent calling getBondState() if the device is null to avoid a nullPointerException.

Frameworks: fix possible NPE on SlimPIE - SlimROM
- some activity chooser (from launchers) give the user choices which do not
exist and would give back a null drawable. To prevend the NPE check the drawable for null

Frameworks/Settings: dynamic PIE menu button + navbar menu logic cleanup - SlimROM
- at least the whole menu button stuff is from android version to android
version more depreciated and will go more and more away. So let us do it
like google:
- clean up the messy old AOKP navbar menu code
- make it only selectable when the menu button is really there
and not as well when it is completly hidden
- remove the menu button action with big icon due off redundancy
- switch between modes: default jb (shows only on request), always and none
- All the above as well now in PIE...small button in first row is added
same selectable modes for the menu lover lol
- smaller adjustments
- settings adjustments

Fix Appbar + removed unused nav code. Due to SlimROM commits, appbar broke.
Frameworks: bring navring/pie/navbar vibrate/sound inline with AOSP
currently all 3 features are doing it a bit different. For navigation
AOSP has for normal click - SlimROM

short soft vibrate + click sound

for longpress

no sound but more intensive vibrate

This commit does:
- seperate keyevents haptic and sound from the other actions and call them
- add vibrate and sound to navring
- navbar only vibrate when the action is performing
- do not use custom vibrate on keycodes
- bring all inline with AOSP like described above
- fix a possible NPE on lockcreen

Allow theming of lockscreen

Settings: fix NPE
- if the user resumes InputMethodAndLanguage settings and the user dictonary preference was already removed before, the user will run into a NPE.

Settings: WiFi: Fix Null Pointer Exception in Wifi Settings dialog
- This patch checks that the activity remains available in the dialog onclick callback before using it.

Settings: WiFi: "Connect" option disappear after rotating.
- The connect option disappears because there is a problem in saving and restoring the state of the access point showed in the dialog box. When a rotation accurs, the framework calls onSaveInstanceState(Bundle outState) of the wifisettings activity. In this method, the state of the access is saved, but not its rssi level. After a rotation, when restoring the access point state, the rssi is initialized to the default value, which means out of range. This is why the connect option is not displayed. I fixed the issue by saving and restoring the rssi level of the access point.

Settings: This fixes crash caused by null pointer (bluetooth)
- The crash is caused by a null pointer. This patch prevents the dereferencement of the pointer when null.

Updated cm source

md5sum: 2c27f2b651a1da54ca1c5c9a1cff4812

[anarky81]

E la vera domanda è...
Ma Temasek non c'ha un cazzo da fare tutto il santo giorno ?!?

Io con il lavoro, la casa etc non c'ho manco il tempo de dormì !!! Ah ah ah...
Cmq tanti tanti complimenti a tutti questi programmatori !!!

[almaximo]

E la vera domanda è...
Ma Temasek non c'ha un cazzo da fare tutto il santo giorno ?!?

Io con il lavoro, la casa etc non c'ho manco il tempo de dormì !!! Ah ah ah...
Cmq tanti tanti complimenti a tutti questi programmatori !!!

non potrete certo dire che non viene manutenuta a dovere .....eheheheheh

[anarky81]

Prima metto la v37 e poi dopo un riavvio flasho da cwm il kernel giusto ?!?

[satoshi]

Prima metto la v37 e poi dopo un riavvio flasho da cwm il kernel giusto ?!?

Se vuoi puoi flashare da cwm prima la rom e poi il kernel senza riavviare tra le due installazioni...