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

Quote:

---

Originariamente inviato da Locaa92

Sulla questione del debrand non so aiutarti perché ho avuto un S3 International, prova a chiedere nel thered di aiuto modding

---

Ma mi consigli di passare alla 4.3 prima di mettere la cyano?

Tutti i problemi che avete di reboot vari sono dovuti ad installazioni sporche.
Dovete piallare tutto e seguire la guida ad inizio discussione !
Unico vero problema che non riesco a risolvere è sull'audio di alcuni giochi che con va... O meglio emette solo rumori metallici.

Per il resto va una bomba !!!

help me provengo dalla MIUI 4.1.2 ho installato l'ultima versione di questa rom ma all'accensione quando mi chiede il pin della sim , non mi sblocca la rete e se vado nelle impostazioni sembra che non senta la rete, devo aggiornare il modem ? se si quale e come.

Quote:

---

Originariamente inviato da wilmo17

help me provengo dalla MIUI 4.1.2 ho installato l'ultima versione di questa rom ma all'accensione quando mi chiede il pin della sim , non mi sblocca la rete e se vado nelle impostazioni sembra che non senta la rete, devo aggiornare il modem ? se si quale e come.

---

Nono il modem nelle cyano non viene toccato, prova a rifare il flash includendo il format system e preload, hai un modem successivo ad mg4? prova a flashare l'ultimo modem MJ9 senza ril

Ragazzi consigliate questa rom o la cm11 originale? in termini di velocità e di stabilità

Quote:

---

Originariamente inviato da GBosso94

Ma mi consigli di passare alla 4.3 prima di mettere la cyano?

---

Io l'ho fatto ma non è richiesto
L'ho fatto soprattutto per ripartire pulito dall'ultima versione ufficiale disponibile

Build V21
md5sum: bcbe24062af3b772466ca2b00bea53ad

CHANGELOG FOR V21

• Fix ART crash during initialization. - @KrissN
  - The CDMAPhone has a static member that initializes a regexp pattern.
  Unfortunately the java.util.regex.Pattern class is not allowed to be called
  during ART bootstrap process which causes a bootloop.
  - To fix this the initialization has been moved into the only method that
  uses this regular expression.
• smdk4412-common: exFAT Support for stock cm kernel
• smdk4412: i9300 update 11 for stock cm kernel
• smdk4412-common: camera: squashed updates from cm-10.2 - dhiru1602
  smdk4412-common: camera: fix EXIF attributes for S5C73M3 sensor
  
  S5C73M3 sensor which is the back camera, doesn't return the EXIF
  attributes using V4L2 IOCTL. This sensor interleaves YUV and JPEG
  frames along with Metadata which contains the EXIF information.
  
  This patch does the following:
  Manually extract the EXIF information from the interleaved metadata
  and implement ISO, Flash, Exposure, Exposure Time and Exposure Bias
  EXIF attributes for S5C73M3.
  Fix incorrect Exposure EXIF attribute that was reporting as 1'.
  
  Change-Id: Id9faa64af498645099cccc9cbf28f2dbdfecd254
  
  smdk4412-common: camera: fix scene mode snapshot capture crashes
  
  Few Scene Modes (like Night, High Sensitivity) if set as default,
  after the camera opens, require the scene mode to be set when the
  stream is turned on inorder to properly take effect. Not doing so
  will result in crashes while trying to capture the snapshot.
  
  Change-Id: I9e6b67c59699495da6922ac737232f58d98c2b40
  
  smdk4412-common: camera: reorganize camera parameters
  
  Few Scene modes require Flash and few don't. However all of
  the scene modes require the focus to be AUTO. Reorganize the
  camera parameters to set the Flash and Focus modes based on
  the scene mode.
  
  Changes adapted from Exynos5 Camera HAL.
  
  Change-Id: If3ab62a1d8aecf84d2a04d1e899f71d4315a66ea
  
  Conflicts:
  
  camera/exynos_camera.c
  
  smdk4412-common: camera: several fixes for autofocus
  
  Setting the AutoFocus off using V4L2_CID_CAMERA_SET_AUTO_FOCUS will
  reset the AF position of the sensor and this was done whenever
  autofocus was completed. This totally defeated the purpose of touch
  to focus since the sensor AF position was being reset after focus
  and had to be refocussed while taking the snapshot. This also led to
  several issues with third party applications since this kind of focus
  behaviour was not intended.
  
  S5C73M3 Back camera Interleaves YUV and JPEG along with metadata. This
  metadata contains the AutoFocus result. Hence we could parse the
  autofocus result instead of using V4L2 IOCTL, which is more efficient.
  Also, the sensor exhibits issues when AutoExposure and AutoWhite Balance
  locks are used with Flash ON. Improper locking could lead to freezing of
  the sensor while taking a snapshot. Hence, only lock AEAWB when flash is
  OFF and unlock them after AutoFocus finishes.
  
  Change-Id: Ief28005dcacd0f8f04990ef8eafebff4a2f109d5
  
  smdk4412-common: camera: enable ZSL mode on front camera
  
  We are querying FIMC2 for the capture output and hence we
  have no reason to restart the preview to have the preview
  resolution match the capture resolution, which is not how
  Zero Shutter Lag works. We could have different resolutions
  for the preview and capture, hence don't stop the preview
  for resizing.
  
  Change-Id: Iaf2b4d0c51dbedb9516b7c3cdde09aa18cd95f73
  
  smdk4412-common: camera: fix incorrect jpeg thumbnail height
  
  Change-Id: I139823883d91ddaa48e2516511539ff5fe150e25
  
  smdk4412-common: camera: fix heap corruption
  
  Change-Id: I0111615b9d4552a7880598a83bc98060fa900b13
  
  smdk4412-common: camera: include support for face detection
  
  Change-Id: I1d176bdf17abdcf0c593fceb01808348b87b75ce
• Active display: Ability to turn off the screen, when a not clearable notification is present
  - Removing the last clearable notification in AD turns of the screen. But if there is a not clearable notification, there is no ability to turn it off directly. This patch adds a power target on place of the 'clear notification' target of AD.
• Pimp up ActiveDisplay
  This is a squashed commit of the following:
  - Active display: turn off display if device gets pocketed again
  - Active display: Option to change display timeout
  - Active display: Add some log output
  - Active display: Add threshold to proximity sensor
  - Display will only be activated if the proximity sensor was covered for 5 seconds or more.
• Fix pimp up ActiveDisplay
  - This is a fix for the new features added with change: https://gerrit.omnirom.org/#/c/2819/
  - 1. Fix the bug when Pocket mode is set to Notifications only and you unlock your device with power key and if you put your hands over proximity sensor the device will turn off (very annoying). The problem was that mWakedByPocketMode it was put in wrong place.
  - 2. Added an option in active display settings for "turn off display if device gets pocketed again" (it's annoying for me, because i cover the proximity very often).
  - 3. Added an option in active display settings for proximity threshold. I use this active display feature as an replacement for "sweep2wake", and when my phone it's on the table, i just want to pass my hand over it to show me the clock or notification (this was ok before the pimp up commit), and now, you can choose how many seconds for proximity threshold.
  - Practicaly, this commit fix one bug, and add settings for the features added in 'pimp up' commit.
• BatteryService: fix FC on boot until battery stat is present
  - updateLightsLocked() can be called from CM's added SettingsObserver when battery stat is not present, causing an FC and a loop until battery stat is present.
• Profile: disable triggers when profiles are disabled
• QS: enable haptic feedback and change Alarm tile longpress - SlimROM
  - nice idea from xploid to have haptic feedback on the tiles just a bit to complicated to do on every tile so activate it centralized as well change the longressbehaviour of alarm tile to the normal onClick behaviour
• QS: make dynamic tiles configurable - SlimROM
  - instead of using a bunch of provider settings var like it was on 4.3 and almost all other roms are doing use one and split like we do for the normal tiles. This
  is more consistent and saves us to observe a bunch of values As well this is integrated into the one layout screen we have. So all QS related is easy and logical usable for the user on one screen
• QS: do not show ringer options on devices which do not support vibrate - SlimROM
  - if a device like grouper does not support vibration it does not make sense to show the settings dialog for it due that this devices just can switch between sound/mute
• Fix and pimp custom lockscreen handle - SlimROM
  - problem on current implementation is that it is not multiDpi compatible. As well it looks a bit weird if the user set a square image always. This commit does
  - introduce central circleimage method to get circle image crops
  - before it was assumed that the height of the handle image is 108px (mdpi base) which is correct but the original handle has a lot unused space around to fit better into the view. Whatever after messurment of the real height 68px is correct of course calculated against the current density
  - both above combined results into a always nice looking custom circle icon on the lockscreen dpi and device undependent
  - saved file in settings calculates the needed image size
  base on the current density.
  - use for custom bitmap our colorize methods due that the result looks way nicer then the usual colorfilter
  - use AntiAlias
• Add temasek shortcuts based on Slim shortchuts - SlimROM
• National roaming info for yesss! in Austria
• National roaming info for Drei in Austria
  - 3AT roams in T-Mobile AT networks
• base: Remove duplicated key handling
• Add "allow disabling call end sound" - Omni
• Address the 'ART' Issue
  Rather than outright remove this completely, address primary concerns:
  
  * Add a more verbose warning message on alert dialog
  * Explicitly state experimental form
  * Explicitly state not supported (no bug reports)
  * Explicitly state issues (crashes, bootloop, etc)
  
  Additionally, move option to 'Apps' header (bottom), as this is it's
  primary impact.
• Only show ART information if switching from dalvik to ART
  - We do not want to confuse users with a big information dialog, if they change from ART to dalvik as dalvik is still the official solution, supported and considered safe.
• Settings: Lockscreen Temasek Handle - SlimROM
  - Grab large temasek icon and resize it rather than process another variable while the lockscreen initilizes.
• Settings: remove preference if device hasn't LockClock installed
• Fix and pimp custom lockscreen handle - SlimROM
  - problem on current implementation is that it is not multiDpi compatible. As well it looks a bit weird if the user set a square image always. This commit does
  - introduce central circleimage method to get circle image crops
  - before it was assumed that the height of the handle image is
  108px (mdpi base) which is correct but the original handle
  has a lot unused space around to fit better into the view.
  Whatever after messurment of the real height 68px is correct
  of course calculated against the current density
  - both above combined results into a always nice looking
  custom circle icon on the lockscreen dpi and device undependent
  - saved file in settings calculates the needed image size
  base on the current density.
• Settings: Long Term Orbits (LTO)
  - Ported from Gerrit Code Review
• settings: Enable location mode header switch
• frameworks/native - gralloc: implement fb_set_swap_interval - Omni
  - https://gerrit.omnirom.org/#/c/3496/
• Updated cm source.

DOWNLOAD SITES

temasek.hopto.org - i9300 / tilapia / grouper
Dev-Host i9300 / tilapia / grouper
AndroidFileHost - i9300
MediaFire- i9300

Dopo il flash dell'aggiornamento va fatto anche quello delle Gapps (ho installato le Banks standard)? Nel caso volessi passare alle PA potrei "approfittare" dell'occasione o rischio di far casini?

Quote:

---

Originariamente inviato da Il Burocrate

Dopo il flash dell'aggiornamento va fatto anche quello delle Gapps (ho installato le Banks standard)? Nel caso volessi passare alle PA potrei "approfittare" dell'occasione o rischio di far casini?

---

nessun casino
flashi la rom poi le gapps poi il kernel (se ne usi uno che non sia quello della rom)
ricordati un wipe cache / dalvik prima o dopo tutti i flash

Ma bisogna sempre flashare la fix cam dopo è il problema è stato risolto?