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

[almaximo]

fatto i wipe e installo la v10 con le PA FULL del 26... stesso errore della galleria che non va visualizzare le foto (neanche altri programmi lo fanno)...

prova a fare un giro con GALLERY REFRESH dal play store
prima però vai nelle impostazioni / applicazioni / tutte cerca il programma della galleria. Arrestalo e cancella cache e dati e fai un riavvio
poi gallery refresh

[almaximo]

Io ora sn con la v8 dite che mi conviene rimanere a questa?

o come si fa a rispondere a una domanda come questa ?
in una fase di sviluppo, tipicamente ogni agiornamento migliora la situazione non la peggiora, poi è chiaro che le opzioni sono tante ma .....

V10 (Current Version)
md5sum: 15d2c3e4e4d9fd24991188bfc127ca82

• FIXED - NPE when on long press POWER button
  - When user did not enable airplane mode in Global menu, it will result in NPE and will reboot the phone.
• Revert "Clear recents screen"
  - Users prefer "shadow" background over clear.
• Revert "Add battery level around unlock ring"
  - This is temporary till I find a way to ensure this works with the new feature
• Revert "CM's Lockscreen - Customizable shortcuts
• Add "Port Lockscreen Targets and Shortcuts" - SlimROM
  First thanks to PA and CM which gave us partly code and some ideas.
  Still some parts of the original implementation are/were buggy as well
  we needed to ehance it.
  
  Whatever the new Slim version is now ready and seems to be completly bug
  free.
  
  - Configurable lockscreen targets...on tablets 8 on phone either 5 or 8
  - configurable lockscreen shortcuts only on phones...up to 5 shortcuts
  - Centralazing some methods....using now then rounded corner on custom
  images systemwide...means on all other shorcut features we have
  - multiDpi compatible
  - new settings logic
  - instance handling of all dialogs like we do on all other places
  way nicer this way
  - tons of fixes
• fb: set correct providers default value am/pm - SlimROM
  - fresh install shows am/pm on english timezones which does not fit with the aosp default behaviour. Go inline with it and hide it as default. User can change it then.
• Add "Active Display" - ChameleonOS
  - Not tested
• smdk4412-common: camera: fix scene mode snapshot capture crashes - dhiru1602
  - 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.
• ART Runtime - "Add verifier: Bypass monitor-{enter,exit} depth checks
  Per Google Bug 61916[1], the monitor-enter and monitor-exit checks in
  dex2oat are excessively strict and will reject some valid APKs, such as
  WhatsApp[2]. This change attempts to relax those requirements." - cernekee
• Updated cm source - lots of it. Help yourself and read it in cm gerrit.

V9
md5sum: 1d57c5bb62de85de9642aa676ed15f8c

• FIXED - Google backup account missing bug in "Backup & reset"
• smdk4412-common: [libhealthd] Proper battery paths
  4.4 introduces a new daemon, healthd, that handles battery status
  - resides in: /system/core/healthd
  - BatteryMonitor.cpp iterates through all the *directories* under
  /sys/class/power_supply looking for a file called 'type'
  - if the type == Battery, it assumes this is the location for the
  battery stats for the device. Only the first directory that matches
  this criteria is used.
  - on msm8660/d2/jf/s2 kernels, this search results in:
  /sys/class/power_supply/fuelgauge.
  - To determine capacity, healthd looks at the contents of the
  'capacity' file under this discovered base path. This results
  in /sys/class/power_supply/fuelgauge/capacity on msm8660/d2/jf/s2
  kernels.
  - Unfortunately, this is the wrong path. The capacity file at this
  location returns a large negative number.
  - Other paths like status, voltage_now, and present are also
  incorrectly determined.
  * For comparison, in 4.3 battery statistics gathering was handled by
  frameworks/base/services/jni/com_android_server_BatteryService.cpp
  - BatteryService does a similar search for a file called 'type' with
  the contents of 'Battery'
  - But the search logic is different here: it takes the *last* path that
  matches the criteria.
  - This results in the correct /sys/class/power_supply/battery
  * This patch overrides the discovery mechanism for battery status completely.
  
• smdk4412-common: [media_codecs] google vpx decoder 4.4 compatible
• smdk4412-common: camera: fix EXIF attributes for S5C73M3 sensor - dhiru1602
  - Ported from cm-10.2
  - 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'.
• vold: pass selinux context to ext4 mount (remount ro)
• Add "Enable quick unlock"
  - Automatically unlock the lockscreen when the correct pin/password is keyed.
• fb: allow navring to show without assisten application - SlimROM
  - this commit adresses two problems
  - If the user does not install google now eg the navring does not show up anymore even when other targets are assigned. Due that we moved the disable/enable controll completley into searchpanelview which calls DelegateHelper to disable it we just can remove the check here in BaseStatusbar
  - 2. On camera widget the navring is disabled and gets enabled afterwards. This is of course a problem if we do not have targets assigned at all. To fix it check for existend targets on the navigation ring.
• fb: cleanup and let the navring stay and not dismiss on targetchange....user seems to like it more this way. - SlimROM
• Add "Kill app back button" to dev options
  - This is for hardware back key
• Dialer: Update Icons to KitKat
• Updated cm source - lots of it. Help yourself and read it in cm gerrit.

mi sembra che ci siano tanti motivi per aggiornare no ?

[piemme22]

Quante ore riuscite a fare di utilizzo? Come va la batteria?

[almaximo]

Quante ore riuscite a fare di utilizzo? Come va la batteria?

un paio di schermo acceso con tutto funzionante, wifi, bluetooth, luce al max, gps,....senza settaggi particolari : zzmove con profilo yank

[piemme22]

un paio? Ovvero?

[almaximo]

Quante ore riuscite a fare di utilizzo?

un paio di schermo acceso

cos'è che non hai capito ? un paio ? schermo acceso ?

[polmone76]

Ciao a tutti, volevo sapere una cosa della fotocamera, con tutte le cm ho avuto sempre il problema della visualizzazione schiacciata durante la registrazione video in FullHD poi mandando il play il video era giusto, ma durante la registrazione non si poteva vedere da quanto era brutto... qualcuno può darmi un feedback su questa versione?

[piemme22]

cos'è che non hai capito ? un paio ? schermo acceso ?

Un paio non vuol dire nulla, 2,3,4,5,100? quanto?

[lionADV]

o come si fa a rispondere a una domanda come questa ?
in una fase di sviluppo, tipicamente ogni agiornamento migliora la situazione non la peggiora, poi è chiaro che le opzioni sono tante ma .....

V10 (Current Version)
md5sum: 15d2c3e4e4d9fd24991188bfc127ca82

• FIXED - NPE when on long press POWER button
  - When user did not enable airplane mode in Global menu, it will result in NPE and will reboot the phone.
• Revert "Clear recents screen"
  - Users prefer "shadow" background over clear.
• Revert "Add battery level around unlock ring"
  - This is temporary till I find a way to ensure this works with the new feature
• Revert "CM's Lockscreen - Customizable shortcuts
• Add "Port Lockscreen Targets and Shortcuts" - SlimROM
  First thanks to PA and CM which gave us partly code and some ideas.
  Still some parts of the original implementation are/were buggy as well
  we needed to ehance it.
  
  Whatever the new Slim version is now ready and seems to be completly bug
  free.
  
  - Configurable lockscreen targets...on tablets 8 on phone either 5 or 8
  - configurable lockscreen shortcuts only on phones...up to 5 shortcuts
  - Centralazing some methods....using now then rounded corner on custom
  images systemwide...means on all other shorcut features we have
  - multiDpi compatible
  - new settings logic
  - instance handling of all dialogs like we do on all other places
  way nicer this way
  - tons of fixes
• fb: set correct providers default value am/pm - SlimROM
  - fresh install shows am/pm on english timezones which does not fit with the aosp default behaviour. Go inline with it and hide it as default. User can change it then.
• Add "Active Display" - ChameleonOS
  - Not tested
• smdk4412-common: camera: fix scene mode snapshot capture crashes - dhiru1602
  - 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.
• ART Runtime - "Add verifier: Bypass monitor-{enter,exit} depth checks
  Per Google Bug 61916[1], the monitor-enter and monitor-exit checks in
  dex2oat are excessively strict and will reject some valid APKs, such as
  WhatsApp[2]. This change attempts to relax those requirements." - cernekee
• Updated cm source - lots of it. Help yourself and read it in cm gerrit.

V9
md5sum: 1d57c5bb62de85de9642aa676ed15f8c

• FIXED - Google backup account missing bug in "Backup & reset"
• smdk4412-common: [libhealthd] Proper battery paths
  4.4 introduces a new daemon, healthd, that handles battery status
  - resides in: /system/core/healthd
  - BatteryMonitor.cpp iterates through all the *directories* under
  /sys/class/power_supply looking for a file called 'type'
  - if the type == Battery, it assumes this is the location for the
  battery stats for the device. Only the first directory that matches
  this criteria is used.
  - on msm8660/d2/jf/s2 kernels, this search results in:
  /sys/class/power_supply/fuelgauge.
  - To determine capacity, healthd looks at the contents of the
  'capacity' file under this discovered base path. This results
  in /sys/class/power_supply/fuelgauge/capacity on msm8660/d2/jf/s2
  kernels.
  - Unfortunately, this is the wrong path. The capacity file at this
  location returns a large negative number.
  - Other paths like status, voltage_now, and present are also
  incorrectly determined.
  * For comparison, in 4.3 battery statistics gathering was handled by
  frameworks/base/services/jni/com_android_server_BatteryService.cpp
  - BatteryService does a similar search for a file called 'type' with
  the contents of 'Battery'
  - But the search logic is different here: it takes the *last* path that
  matches the criteria.
  - This results in the correct /sys/class/power_supply/battery
  * This patch overrides the discovery mechanism for battery status completely.
  
• smdk4412-common: [media_codecs] google vpx decoder 4.4 compatible
• smdk4412-common: camera: fix EXIF attributes for S5C73M3 sensor - dhiru1602
  - Ported from cm-10.2
  - 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'.
• vold: pass selinux context to ext4 mount (remount ro)
• Add "Enable quick unlock"
  - Automatically unlock the lockscreen when the correct pin/password is keyed.
• fb: allow navring to show without assisten application - SlimROM
  - this commit adresses two problems
  - If the user does not install google now eg the navring does not show up anymore even when other targets are assigned. Due that we moved the disable/enable controll completley into searchpanelview which calls DelegateHelper to disable it we just can remove the check here in BaseStatusbar
  - 2. On camera widget the navring is disabled and gets enabled afterwards. This is of course a problem if we do not have targets assigned at all. To fix it check for existend targets on the navigation ring.
• fb: cleanup and let the navring stay and not dismiss on targetchange....user seems to like it more this way. - SlimROM
• Add "Kill app back button" to dev options
  - This is for hardware back key
• Dialer: Update Icons to KitKat
• Updated cm source - lots of it. Help yourself and read it in cm gerrit.

mi sembra che ci siano tanti motivi per aggiornare no ?

da quando ho aggiornato il global menu (menu che si apre tenendo premuto il tasto di accensione) non c'é piu e se lo premo mi si riavvia il dispositivo. Soluzioni? grazie mille per eventuali risposte

[Volpe92]

Ragazzi, avete qualche feedback con Whatsapp + ART con la nuova v10??