[ROM][I9300][4.4.4] Temasek's UNOFFICIAL CyanogenMod 11

[Linex]

@kani

Danke. Laut deiner Anleitung problemlos.

 

[salva76]

Wo schalte ich GPS ein? Und wie kann ich es den Kachel hinzufügen?

 

[Odin666]

GPS siehst du bei Standort unter Einstellung. Kacheln einfügen lässt bei Temasek Erweiterung dann unter Benachrichtigung dann Kacheln

 

[Odin666]

Also wenn ich mit Apollo Musik höre bei Display an läuft Musik flüssig aber wenn Display off dann hackt Musik dermaßen.

 

[nobody573]

Also ich höre mit Poweramp und hab keine Probleme

 

[Odin666]

DSP Manager eingefroren dann funzt Musik bei Display off

 

[Enkidu]

Moin moin...

Seitdem ich auf CM11 mit Boeffla-Kernel und Xposed/Xprivacy bin rebooted sich mein S3 immer mal wieder. (Unter CM10.1 mit sehr ähnlicher Konfiguration hatte ich sowas nicht...)

Ich hab Null Plan, ob das nun mit der CM11 oder Boeffla oder X* zu tun hat. Daher hab ich auf XDA mal nen eigenen Thread aufgemacht, inkl. ein paar Logcats der Reboots.

Nachdem ich jetzt nicht viel Ahnung von der Materie hab, vielleicht kann mir jemand helfen, damit ich herausfinden kann, was da abgeht und das Problem an den Richtigen adressieren kann.

==>> HIER LANG <<==


Merci schonmal,
Enkidu

 

[Kani_23]

Hast du dir eventuell bei Xprivacy ne Einstellung zerschossen?
Denn diese Kombination haben hier glaub ich einige.
Schon mal neu aufgesetzt?

Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App

 

[B@sti]

Muss man um die Performance des Handys mit diesem AnTuTugedöns zu testen noch irgendwelche Einstellungen vornehmen? Habe den boeffla auf zzmove Standard mit 1600MHz, weiß allerdings nicht all zu viel über die Profile (ja, ich weiß - sind auf der Seite erläutert).

--------------


ZZMOVE Standard - 20386 Punkte

ZZMOVE Performance - 21000 Punkte

--------------

Bin ich mal gespannt ob die ROM von Smokedroids Kumpel echt so rasant ist.

 

[diginix]

Yeah, digitaler Schwanzvergleich...
Ich hab mit 2000 MHz 30000 Punkte

 

[B@sti]

Es geht mir um die Performanceunterschiede der ROMs auf meinem Gerät. Wenn du Penisneid hast, tut mir das leid.

 

[ThatGangsta]

Ich hab wohl den kleinsten
zzmove - battery yank extreme bei 1200Mhz: 12197 Punkte

Trotzdem lagfreies System und super Akkulaufzeit.

 

[Yprh]

Bin dann wohl das zwischen ding von euch mit 18150.
Zzmoove yank battery. 2000-13000 MHz

Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App

 

[B@sti]

Ich hab wohl den kleinsten
zzmove - battery yank extreme bei 1200Mhz: 12197 Punkte

Trotzdem lagfreies System und super Akkulaufzeit.

Naja, don't feed the troll.

Hab auch nun battery yank extreme drin. 1200Mhz reichen auch völlig aus, denke ich. Spiele sowieso keine Hardcoregames auf meinem S3.

LG

 

[ThatGangsta]

Ich verwende diese Konfiguration seit ich den Boeffla-Kernel habe, Spiele laufen trotzdem alle.

OT:

Ich hab vorhin meinen 1000sten Post für so was niveauloses verschwendet

 

[Kani_23]

@thatgangster
Battery extrem yank mit 200-1200MHz mit 15684 arbeite mit Art.
Interessant das der wert dabei so streut oder benutzt du dalvik?

Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App

 

[ThatGangsta]

Mir fällt auf, dass ich da ein paar Threads durcheinander geschmissen habe.

Ich bin gerade auf der OmniRom vom 15.12., benutze ART.
Von daher gehört mein Benchmark eigentlich nicht hier hin.

 

[thisisme]

Bin dann wohl das zwischen ding von euch mit 18150.
Zzmoove yank battery. 2000-13000 MHz

Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App

rly, 13.000MHz, also, 13 GHz auf dem S3? wie viel willste dafür

Habe mit zzmoove battery, 200-1400 MHz, medium CPU UV und ART 18606 Punkte.

Habe keinerlei Lags und trotzdem lange Akkulaufzeiten

 

[Yprh]

Hahah ja das ist die NASA Version des s3. Ne war natürlich nur ein Tipp Fehler meinte 1300 MHz
Edit:
Benutze auch nicht Art sondern Delvik wegen xposed


Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App

 

[Yprh]

Version 21 ist da!

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 kernelsmdk4412: i9300 update 11 for stock cm kernelsmdk4412-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: I1d176bdf17abdcf0c593fceb01808348b87b75ceActive 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 disabledQS: 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 behaviourQS: 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 screenQS: 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/muteFix 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 AntiAliasAdd temasek shortcuts based on Slim shortchuts - SlimROMNational roaming info for yesss! in AustriaNational roaming info for Drei in Austria
- 3AT roams in T-Mobile AT networksbase: Remove duplicated key handlingAdd "allow disabling call end sound" - OmniAddress 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 installedFix 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*http://review.cyanogenmod.org/#/c/51422/3settings: Enable location mode header switchframeworks/native - gralloc: implement fb_set_swap_interval - Omni
-*https://gerrit.omnirom.org/#/c/3496/Updated cm source.



Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App