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

  • 5.275 Antworten
  • Letztes Antwortdatum
und das mit dem Sekunden Aussetzern beim Abspielen von Liedern das hatte ich vorher auch noch nicht gehabt und beim kratzen wird dadurch aber nicht die Hardware beschädigt oder?
 
Also das Sekunden Aussetzer hat ich noch nie nur das Kratzen.
Bis auf das es in den Ohren weh tut ist meinen Earphones nix passiert.
 
V8 ist verfügbar :D


bestimmt noch ne Urlaubs Version :)


Gesendet von meinem GT-I9300
 
Zuletzt bearbeitet:
  • Danke
Reaktionen: kloppi123 und kmr100
Build V8
md5sum: 9c3da26f93beac6cda7e076b373e757c

CHANGELOG FOR V8


  • Fix external sdcard mountpoint
    - Reference -> http://forum.xda-developers.com/show....php?t=2537793
    - frameworks commit
    - smdk4412-common commit
  • smdk4412-common: Add "Export SECONDARY_STORAGE /storage/sdcard1" to init.smdk4x12.rc
  • i9300_audio_hw: Fix first recording sound path setup - Omni
    - On initialize - disabling voicecall route before setting default input and output devices makes proper registers setup persist.
  • system wide immersive mode aka expanded desktop - SlimROM
    - To enable expanded desktop ---> Navigation -> Global Menu
  • fb: Fix FindBugs issues
    - IntProperty: Infinite recursive loop
    - SQLiteSession: Null pointer dereference
    - UsbStoreActivity: Null pointer derefence
    - LocationManagerService: No relationship between generic parameter and method argument
    - ActivityManagerService: Call to equals() comparing different types
    - ChooseAccountTypeActivity: Possible null pointer dereference
    - RuimRecords: Possible null pointer derefence
  • Don't start keyguard in an attempt to exit it. - Danny
    exitKeyguardSecurely() will open the keyguard if it's currently disabled by an app. As this is unwanted here (the user has either already bypassed the keyguard or the keyguard isn't secure; otherwise he couldn't click on a notification entry) and as the lockscreen already is dismissed a few lines above, don't call exitKeyguardSecurely here.
  • SystemUI: fix RecentPanel position in landscape mode. - mik9
    - In landscape mdoe we forcing ltr layout direction. This cause call to resolvePadding too late and discards paddings computed by fitSystemWindows. To workaround this we can catch onRtlPropertiesChanged and force executuin of fitSystemWindows one more time. To fix scroll issue after padding will be setted
    we calling scrollTo with correct position.
  • fb: fix recents animation on new immersive mode - SlimROM
    - thanks here as well for identify the problem to Kiril. But I changed the implementation. Beside that we give the user the ability to setup different navbar heights IMO there is absolutly no need to use an observer to get the status. We can fetch this from WindowManagerService to get all needed information.
    - So at least this patch fetches needed values from WindowManager and calculates in the missing heights.
  • fb: 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.
  • Keyguard: Set WIDGET_CATEGORY_KEYGUARD when AppWidgetHostView is created - sam3000
    - Allows the default lockscreen widget to inherit the keyguard widget host category. Without this, only widgets added through KeyguardActivityLauncher are assigned the correct OPTION_APPWIDGET_HOST_CATEGORY.
  • StorageManager: fix android.process.media process stop while plug a discontinuous partitioned SD Card.
    - While get volume state, throw an IllegalArgumentException, catch this exception in StorageManager and return null to MtpService to avoid process stoping.
  • fb: Remove possible leak when exception occurred.
    - nameUtf8 is not released after exception. In addtion, Fix code going down after ThrowException.
  • Wifi: Fix for connection failure between third client and GC.
    - When third device sends a connection request to the group client, the existing connection is terminating and also the ongoing connection not successful.Currently as there is no use case where third device is connecting to GC,and the existing onnection getting terminated.This is addressed by ignoring the new connection request from third client to GC and the existing connection is intact.
    - CRs-Fixed: 467049
  • SystemUI: Add missing recycle calls
  • Correctly set the animation flag of the ActionBar
    - Showing/hiding the ActionBar is intentionally done without any animation when done while the Activity is not visible (between onPostResume and onStop). The issue is the animation flag was not set at all when the ActionBar was initialized (i.e. getActionBar() called) between these two lifecycle methods (because mActionBar was null).
    - A temporary solution is to call getActionBar() to initialize the ActionBar in onCreate().
    - This patch simply keeps a flag of the current animation state and update it whenever the ActionBar and/or the flag has been modified.
  • Update the layer's alpha value upon composition of the layer
    - Fixes: This patch makes sure that the layer's alpha value is up-to-date and does not reflect the previous view's alpha value. it fixes the square block on marquee fading edge when text view is applied transparency.
  • Memory leak in IInputMethodSessionWrapper executeMessage
    - In some cases the executeMessage is called with mInputMethodSession == null. For the messages DO_UPDATE_SELECTION, DO_APP_PRIVATE_COMMAND
  • Fix NPE in ConnectivityService
    - Could occur when requestRouteToHostAddress is called on a network with no associated tracker. Code later in the method handles this case gracefully but code introduced in JB throws an exception.
  • Fix a JNI local reference leak in JNIMediaPlayerListener::notify.
    - Bug: https://code.google.com/p/android/is...etail?id=62137
  • SystemUI: update internal state right after hiding transient bars.
  • Keyguard: smooth background change.
  • Fix a programmatic smooth scroll bug
    - Bug: smoothScrollToPosition() stops at child view of which height is higher than list view itself.
  • Clear recents screen
  • Move Mms from phone specific to telephony - SUCCESS
    - Tablets want MMS too (carriers send messages, etc), lets make this for any device inherenting telephony.mk
    - This is applicable to my tilapia build so that outgoing sms/mms can be sent without issue.
  • Updated cm source
 
  • Danke
Reaktionen: Saintscar, nobody573 und Mopp
wurde das mit dem Sound beim Speerbildschirm mit der Version auch gefixt?
 
Also ich bin zwar erst ab der 10.2 Cyanogenmod Jünger aber nun völlig überzeugt. Nach der Laufzeit Umstellung auf Art und dem losketten des Prozessor im Boeffla Kernel kommt mein Handy über die 20k im Benchmark. Was habt ihr da für Erfahrungen bzw für Daten. Könnt mich diesbezüglich ja mal mit einer Person anschreiben, wollen hier ja nicht alles mit off topic zu spammen. Würde mich nur mal interessieren.

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

Anhänge

  • uploadfromtaptalk1385330726191.jpg
    uploadfromtaptalk1385330726191.jpg
    22,8 KB · Aufrufe: 412
Könnte einer eine Übersicht erstellen, was noch nicht funktioniert? Ist die Performance mit CM10.2 vergleichbar? Gestern hatte ich die unoffizielle Temasek-Version drauf und war nicht so begeistert.
 
Ich hatte einige Tage die Temasek-Rom drauf und war sehr zufrieden. Ich hatte allerdings den Boeffla-Kernel. Es funktionierte alles. Jetzt bin ich aber wieder auf cm11 unoffiziell. Aber nicht weil ich mit Temasek unzufrieden war.
 
Was ist denn bei der unofficial anders? (Außer, dass die temasek features nicht enthalten sind)
 
Du hast dir die Frage gerade selbst beantwortet.
 
  • Danke
Reaktionen: tbremer19
Lässt es sich bei deaktivierten Sperrbildschirm irgendwie verhindern, dass man beim Aktivieren aus dem Standby ständig im Taskmanager landet? Das nervt ja tierisch!
 
Kann es sein das der lautlos toggle nicht funktioniert
 
wollte mal wissen, wo man denn autostart für APPs einstellen, die dann der Taskkiller nicht stoppt.
boeffla-kernel-CM-2.1-beta1-cm11.0-r3p2 nutzte ich läuft sehr gut.
 
Version 9 ist raus
 
  • Danke
Reaktionen: nobody573
Was für Modems benutzt ihr so?
Habe MG4 und 2 von 4 anrufen (eingehend) mussten heute wiederholt werden, weil nichts zu hören war :(
 
hier mal der Changelog

V9 (Current Version)
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.
 
Nabend zusammen,

werden hier jetzt exFat SD-Karten unterstützt?
Hab mir jetzt den Boeffla geflasht aber leider kann ich meine SD Karte nicht nutzen,
da sie nicht gefunden wird. Danke
 
Du musst das exfat Modul in der config App aktivieren (verschiedenes)
 

Ähnliche Themen

html6405
Antworten
27
Aufrufe
5.690
Verci
V
html6405
Antworten
15
Aufrufe
6.657
html6405
html6405
Zurück
Oben Unten