ROM: [CM10.2][4.3][ROM][KERNEL] temasek's UNOFFICIAL Build

För mig startas Google sök. Jag kör med 5 mjukvaruknappar.

 

Nu fungerar det helt plötsligt

Kör också med 5

Sent from my GT-I9300 using Tapatalk 2

 

Älskar CM 10.2 men skulle behöva s-planner måste nog gå tillbaka till stock om jag ska kunna använda den :-(

Skickat från min GT-I9300 med Tapatalk 4

 

Testa Google keep.

/Tapatalk 4 Beta

 

v36!

Nu fick jag även skapa ett Cyanogenmod konto

EDIT: finns en experimentell kernel med. Så en ny stabil lär dyka upp underdagen

 

Fet uppdatering på v37!

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

 

Oh herregud! Tror jag går tillbaka till temasek tills Ls gått ut från beta stadiet

Sent from my GT-I9300 using Tapatalk 2

 

Kan man använda sig av expanded desktop utan att navbaren försvinner?

Sent from my GT-I9300 using Tapatalk 2

 

Kan bara hålla med. LS är instabil på 4.3 och jämför man det med Temasek's build, så är det som dag & natt mellan båda.

 

bytte till xxufme7 modemet som alla pratar om över på xda. Och visst hade de rätt.. klart bättre batteritid, drar nästan 0 idle..

tt4

 

Vart hittar du den utan RIL? För man ska väl inte ha modem+RIL zips då de inte är kompatibla med AOSP?

 

drog hem den de länkade till i temasek xda tråd.

har nästan 16h och 89% kvar på batteri... iofs bara 34min skärmtid.

tt4

 

Får man dra in de modemet då

Sent from my GT-I9300 using Tapatalk 2

 

Någon risk med att flasha modemet?

Hittade denna filen i tråden på XDA
modem_CWM_I9300XXUFME7
http://d-h.st/r5z

 

nix, inte mer än när du flashar i vanliga fall...
Alltid backup av efs med ktool..(man vet aldrig när olyckan är framme)

Screen på min upptid:
70% kvar på batteri efter ~29 timmar.. 1,5 timme skärm.
Fantastiskt strömsnål idle, drar nästan 0..

Temasek v37 med senaste Temasek boeffla-noabb kernel.
Greenify alla appar utom de jag vill ha sync på.
UFME7 modemet.
Screenlight = ~10-15 %
3st widgets på hemskärm.
wifi alltid på.

 

Oj, ser ju grymt ut!

Har fått någon konstig fördelning på interna minneskortet sen jag flashade denna. Har 2 uppsättningar filsystem, det ena ligger under /0 på minnet. Kan inte se det i datorn och har bara 700 Mb ledigt på inbyggda.

"emulated" kallas inbyggda minnet om jag kollar i filhanterare...

 

Räcker det att man gör en backup på EFS via Andromizer måste jag göra något med denna fil?
Eller är det sen bara att flasha in detta?
Och tömmer denna hela telefon minnet?

Skickat från min GT-I9300 med Tapatalk 4

 

Jag har ingen telefon längre iaf, nu är det en vit surfplatta. Mitt IMEI är borta. Så kan det tydligen gå

 

I ktool är det bara att restor efs på backupen man gör i det programmet..
Och nej, den raderar inte sd.

Gjorde följande för ca 2 månader sen.. och det gick som smort.

@grief
Har du en efs.img och en efs.tar.gz på sd? (efs backup)
Då är det bara att köra restore på dessa.

För du tog väl backup med ktool som jag sa?

 

Ja, har en efs.img, den kör restore men det diffar fortfarande på datastorleken vid omstart när man kollar i programmet.

Någon tar.gz-fil har jag inte.