Ho notato sul sito di Temasek in "privato" una V42-1 del 04/02/2014 ne sapete qualcosa?
04-02-14, 11:04
kijuz
Bella questa 42.. Migliorata davvero la gestione della localizzazione. Tra l'altro la possibilità di bloccare l'auto start delle app introdotta qualche versione fa è una manna per bloccare il wakelock NFC.. Bene temasek!!
04-02-14, 14:24
lalaspdn
Quote:
Originariamente inviato da pipolo0
Ho notato sul sito di Temasek in "privato" una V42-1 del 04/02/2014 ne sapete qualcosa?
Contiene la novità del sound pack (Omnirom audio theme). Versione senza supporto da parte di Temasek perché solo di test, probabilmente in attesa di una V42 ufficiale che lo implementi.
Penso si tratti della possibilità di "temare" i suoni di sistema (selezione, tastiera, fotocamera, ecc ecc) un po' come si fa per i temi che modificano la grafica.
I temi vanno scaricati a parte.
06-02-14, 08:20
kijuz
La musica inizia a saltare anche a me a schermo spento.. Ma disabilitando qualsiasi personale spunta in DSP MANAGER il problema sembrebbe scomparire. Provate
06-02-14, 09:11
criiistian
ho installato la 42.1 ma non trovo questi settaggi. dove li trovo?
06-02-14, 14:17
lalaspdn
Quote:
Originariamente inviato da criiistian
ho installato la 42.1 ma non trovo questi settaggi. dove li trovo?
Impostazioni > audio > sound packs
07-02-14, 05:02
Axospirit
Sono alla 42 e non so a voi ma pare essere molto stabile. Sino ad oggi ho provato svariate vs di aosp e vuoi per un motivo o per un altro,a lungo termine le rom divenivano instabili. Con la 42 ho usato il launcher di default(quello del team CM) e il kernel stock. Con questa accoppiata non impuntamenti di nessun tipo né arresti di applicazioni. La domanda che viene da farsi è se questi fantomatici kernel facciano più danni che altro..anche il launcher è stabile..avete dei riscontri? Per cio che riguarda la batteria arrivo a 2ore di schermo con dati attivati
Sono alla 42 e non so a voi ma pare essere molto stabile. Sino ad oggi ho provato svariate vs di aosp e vuoi per un motivo o per un altro,a lungo termine le rom divenivano instabili. Con la 42 ho usato il launcher di default(quello del team CM) e il kernel stock. Con questa accoppiata non impuntamenti di nessun tipo né arresti di applicazioni. La domanda che viene da farsi è se questi fantomatici kernel facciano più danni che altro..anche il launcher è stabile..avete dei riscontri? Per cio che riguarda la batteria arrivo a 2ore di schermo con dati attivati
Add "Add Dialer suggestions and reverse lookup" - OmniROM
- Dialer suggestions based on OSM
- Options are turned off by default, can be enabled in Phone > Settings
- Reverse lookup supported countries: US , CH, FR
frameworks/base: Lockscreen Notifications: rewrite add notification logic
- There were some problems with notifications getting replaced while the user was currently dragging them. This commit should fix that by always waiting until animations and user input are finished before replacing a notification view.
frameworks/base: Vpn: Setup routes
frameworks/base: Prevent MediaScanner infinite loop with invalid path
- including double slash "/storage/sdcard0/xx//xxx/xxxx"
frameworks/base: fix on tablets notification drawer height on custom image background
- The measurment bases always on the height of the complete view. Due that we set an image as background (does not make a difference if we do it like now with an image view or set the background resource for the complete view) the image is calculated into the measured height as well which leads into the problem the the panel completly opens to the bottom.
- To prevent that measure only the real content and decide based of this value how much the rubberbands should go into action. This will be only done on devices which set a minimum height for the drawer which indicates that we need to measure the content more exactly.
frameworks/base: restore navbar compatibility with several xposed modules
frameworks/base: frameworks: Remove KeyguardTestActivity (Hope systemui improved battery life …)
frameworks/base: storage: Don't list removed volumes in storage list …
- Don't tell apps that USB storage or empty SD slots are available for use. This fixes errors about trying to create dirs in vold as well as the relevant CTS cases.
frameworks/base: AppOps: fix allow/reject counting …
- Was missing from the original counters commit: Gerrit Code Review
frameworks/base: Quick Record Tile Save Location …
- Quick Record Tile now saves the file in Podcast folder inside your SDCard.
frameworks/base: Fix NPE causing a hot reboot when pressing power button
frameworks/base: SUPL early data connection fix …
- if GPS started before data connection is alive, SUPL will be broken for entire power cycle.
frameworks/base: GlobalActions: Set the initial status of airplane mode toggle …
Actually, the initial status of airplane mode toggle is set to false
when the power menu dialog is initialized.
- This causes an issue if you set airplane mode and then reboot. After the reboot, the dialog displays the wrong airplane mode status, eg. "Airplane mode is not active", and if you toggle that option, a wrong intent is sent again to put ON the airplane mode, instead of OFF, the toggle (that is in transition state) will be set disabled.
- This commit fixes this issue.
frameworks/base: Add Fast Charge QS Tile …
- This includes a file observer to watch the sysfs file change
frameworks/base: Speedup kill app timeout delay
- from 2000ms to 1000ms
frameworks/base: Fix for the race in Wallpaperservice …
- Wallpaperservice has a race among message handler of DO_DETACH and service's onDestroy. In certain cases, the engine kept track in mActiveEngines is removed by message handler of DO_DETACH and service's onDestroy
doesn't get a entry in mActivieEngines and isn't able to invoke detach. This keeps the broadcast receiver, mReceiver active and is unregistered by the framework and a corresponding leak is reported.
- Later, the message handler of DO_DETACH continues and invokes detach on mEngine, which attempts to unregister mReceiver and framework throws an exception "Receiver not registered: android.service.wallpaper.
WallpaperService$Engine$1@40874580" and causes the framework to reboot.
- In case of system_server, WindownManagerPolicy and android.server.ServerThread contest for access of shared members, mActiveEngines and mEgine. Fix is to protect the critical section via synchronized block.
Settings: Don't crash if we pause too quickly
- Notifier is unregistered in every case in pause. However, if you close the Settings app too quick, the notifier might not be registered at all, causing an IllegalArgumentException during the unregistering.
Settings: Enable Back-key when go to Emergency call …
- When go to "Emergency call" from lock screen, back key is disappeared. It is difficult for user to find the way to go back to previous screen. This might be bad user experience. So we are going to make it enable.
Settings: PrivacyGuard: confirm permissions reset …
- The button to reset all application permissions to enabled looks suspiciously like a refresh button. Prompt the user with a confirmation dialog to make sure they know what they've pressed.
Serve a settare le connessioni del telefono,
Prova andare in Setting - wireless e reti - Connection manager
07-02-14, 15:27
pipolo0
Ho scaricato da siti diversi la v43 ma quando la vado a flashare dopo aver fatto i vari wipe mi da failed le precedenti nessun problema qualche dritta?
07-02-14, 15:29
criiistian
Da me ha funzionato tutto perfettamente, prova a riscaricarla e sta attento che la scarichi del tutto perche una volta è successo a me e mi dava lo stesso errore
07-02-14, 15:42
pipolo0
Quote:
Originariamente inviato da criiistian
Da me ha funzionato tutto perfettamente, prova a riscaricarla e sta attento che la scarichi del tutto perche una volta è successo a me e mi dava lo stesso errore
ne ho scaricato 6 versioni diverse da vari siti ma niente torno alla 42 e tutto ok bhò forse il mio cel non la digerisce la V43 con la 41 faceva lo stesso al 3 tentativo poi è andata
07-02-14, 16:38
ClaudìoS3
Ragazzi ho messo a un mio amico sempre con s3 questa temasek da qualche gg e sembra molto buona.. il problema è che sta riscontrando un consumo eccessivo di com.android.systemui addirittura il 10 %
Cosa può essere? Come rimediare a questo problema?
07-02-14, 17:12
pipolo0
Quote:
Originariamente inviato da pipolo0
ne ho scaricato 6 versioni diverse da vari siti ma niente torno alla 42 e tutto ok bhò forse il mio cel non la digerisce la V43 con la 41 faceva lo stesso al 3 tentativo poi è andata
Niente da fare ho scricato tutte le versioni dei vari siti ma mi da sempre "Failed" aspetto la V44
07-02-14, 17:47
satoshi
Quote:
Originariamente inviato da pipolo0
Niente da fare ho scricato tutte le versioni dei vari siti ma mi da sempre "Failed" aspetto la V44
Hai provato a controllare se l'md5 corrisponde a quello giusto? Prova a usare un diverso browser per scaricare la rom.
07-02-14, 23:22
pipolo0
Quote:
Originariamente inviato da satoshi
Hai provato a controllare se l'md5 corrisponde a quello giusto? Prova a usare un diverso browser per scaricare la rom.
Ho provato in tutti i modi Crome, explorer, mozilla ma niente non me lo installa
08-02-14, 07:58
lalaspdn
Quote:
Originariamente inviato da pipolo0
Ho provato in tutti i modi Crome, explorer, mozilla ma niente non me lo installa
Prova ad usare questo torrent, magari avrai più fortuna.
Ps: che recovery usi?
[URL]https://www.dropbox.com/s/z928fm2bbpv9w0b/cm-11-20140206-UNOFFICIAL-temasek-i9300-V43.zip.torrent[URL]
08-02-14, 08:08
pipolo0
Quote:
Originariamente inviato da lalaspdn
Prova ad usare questo torrent, magari avrai più fortuna.
Ps: che recovery usi?
[URL]https://www.dropbox.com/s/z928fm2bbpv9w0b/cm-11-20140206-UNOFFICIAL-temasek-i9300-V43.zip.torrent[URL]
Ho la TWRP 2.6 etc... ma con le versioni precedenti tranne un'episodio con la V41 ( scaricata 3 volte ),non ho mai avuto problemi dopo il "Faled" della V43 rimonto di nuovo la V42 senza problemi ora ci provo grazie
08-02-14, 08:34
anarky81
Metti CWM 6.0.4.4 e vedrai che tutto andrà benone !!!
08-02-14, 08:51
Volpe92
Quote:
Originariamente inviato da anarky81
Metti CWM 6.0.4.4 e vedrai che tutto andrà benone !!!
C'è anche la CWM 6.0.4.7 ;)
08-02-14, 11:58
ClaudìoS3
CWM 6.0.4.7 (ULTIMA) TOUCH E NON TOUCH FLASHABILE DA RECOVERY E DA ODIN:
Io attualmente ho la TWRP posso flashare la CWM 6.0.4.7 dalla recovery o da Odin, poi va a sostituire automaticamente la TWRP? io con questa recovery che ho mi trovo bene dite che risolvo?
08-02-14, 19:15
lalaspdn
Quote:
Originariamente inviato da pipolo0
Io attualmente ho la TWRP posso flashare la CWM 6.0.4.7 dalla recovery o da Odin, poi va a sostituire automaticamente la TWRP? io con questa recovery che ho mi trovo bene dite che risolvo?
Puoi farlo direttamente dalla recovery flashando il file zip e secondo me hai buone possibilità di risolvere anche il tuo problema di flash della 43...
08-02-14, 21:12
pipolo0
Quote:
Originariamente inviato da lalaspdn
Puoi farlo direttamente dalla recovery flashando il file zip e secondo me hai buone possibilità di risolvere anche il tuo problema di flash della 43...
Allora messa su la CWM 6.0.4.7,montata la V43 riavvio del cel e mi alterna Samsung S3 poi Recovery e cosi via ma il cel non parte ho dovuto rimettere di nuovo la 42
08-02-14, 22:03
satoshi
Quote:
Originariamente inviato da pipolo0
Allora messa su la CWM 6.0.4.7,montata la V43 riavvio del cel e mi alterna Samsung S3 poi Recovery e cosi via ma il cel non parte ho dovuto rimettere di nuovo la 42
Hai fatto i wipe prima del flash?
08-02-14, 22:16
pipolo0
Quote:
Originariamente inviato da satoshi
Hai fatto i wipe prima del flash?
Si fatto i wipe cashe e devilk ho fatto l'installazione 2 volte ma nisba fatto strano e che l'installazione con la nuova recovery va fino in fondo non fa "failed" forse la diversità della recovery ma il cell rimane su Samsung S3 e non si avvia e va in recovery di nuovo e questo mi dà con una certa palpitazione
08-02-14, 22:47
satoshi
Quote:
Originariamente inviato da pipolo0
Si fatto i wipe cashe e devilk ho fatto l'installazione 2 volte ma nisba fatto strano e che l'installazione con la nuova recovery va fino in fondo non fa "failed" forse la diversità della recovery ma il cell rimane su Samsung S3 e non si avvia e va in recovery di nuovo e questo mi dà con una certa palpitazione
Se hai un nandroid prova con un full wipe (compreso un wipe data). Altrimenti aperta la 44...
08-02-14, 23:07
pipolo0
Quote:
Originariamente inviato da satoshi
Se hai un nandroid prova con un full wipe (compreso un wipe data). Altrimenti aperta la 44...
Scusa satoshi ma avendo fatto un nandroid con TWRP, posso richiamare tutto con la CWM? ora ho il cell che và una favola personalizzato con appl ed altro mi dispiacerebbe fare tutto d'accapo aspetterò la 44 poi si vedrà
08-02-14, 23:17
satoshi
Quote:
Originariamente inviato da pipolo0
Scusa satoshi ma avendo fatto un nandroid con TWRP, posso richiamare tutto con la CWM? ora ho il cell che và una favola personalizzato con appl ed altro mi dispiacerebbe fare tutto d'accapo aspetterò la 44 poi si vedrà
Non sempre recovery diverse hanno nandroid compatibili tra di loro... meglio non rischiare.
Se hai trovato un buon compromesso io non dico altro. :beer:
10-02-14, 18:28
pipolo0
Pensate che Temasek rilasci qualche altra versione? o è finita con la V43
10-02-14, 20:42
uzzz
In upload ha messo la 43.1 che la trovi domani disponibile .... e a breve rilascerà la 44
11-02-14, 13:17
Il Burocrate
Build V45
i9300 - md5sum: 647464a92b0c6d7601579cbc4bd5b468
*** IMPORTANT ***
This instructions are for i9300 / tilapia & grouper only, hlte family not affected.
SlimPIE implementation prior to cm11 was different and as a result affected your preferences and may triggers a Settings FC. When this happens, as a normal user you are required to perform a FULL WIPE.
Who needs a FULL WIPE?
1. Flashing V45 and selecting SlimPIE in Navigation triggers a Settings FC. If you don't use SlimPIE then you don't have to wipe but if you wants SlimPIE then pls backup your apps+data, perform a FULL WIPE and then flash your V45/gapps/kernel again.
Who doesn't needs a FULL WIPE?
1. Flashing V45 and selecting SlimPIE in Navigation does NOT trigger a Settings FC.
CHANGELOG FOR V45
Spoiler:
Add "Open source google dialer and more" - SlimROM
This is an open source variant of the well known google Dialer which gives the
ability to show nearby places and revese lookup. It uses default the Google
engine to do this. As well you have the ability to use other providers.
Revert "ActiveDisplay (rework interface)"
- SystemUI FC on my tilapia
- Will re-visit this later
Revert "Add Dialer suggestions and reverse lookup" - OmniROM
- This revert is to give way to open source dialer.
frameworks/base: EdgeGestureService give abbility to reduce the left and right trigger height if IME shows up
- This patch gives the abbility that features can set the IME_CONTROL flag in addition to the position flags to enable reducing trigger heights on the left and right edge to avoid conflicts with swipe keyboard.
- Although the inputfilter lets come presses to the application trough the normal user behaviour is to start keyboard swiping before they really even pressed the char button which results in conflicts with whatever feature is using the left and right edge as trigger.
- Features who want to use it need to set IME_CONTROL flag. As well if notification drawer was pulled down or global menu is shown on top of the IME keyboard the original size gets restored till they are dismissed/closed
- This patch adds only the support for it.
frameworks/base + Settings: SlimPie give user ability to reduce trigger heights if IME keyboard shows
- Add a user option to reduce left and right trigger of SlimPie if keyboard shows up (especially usefull for swipe keyboard which most keyboards are nowadays). Enabled by default user can disable it in settings.
frameworks/base: TRDS fix possible UI freeze on auto mode change
- only call on theme mode change when auto mode changes. Under special conditions
it can happen that it is called twice
- ensure that whenever a mode change is really done to close the notification shade
- minor cleanup
Browser: blue to grey browser's progress bar - SlimROM
CHANGELOG FOR V44.1
- For i9300 users who's last buld was V43 and now this build is V45.
Spoiler:
Added "SlimPie" - SlimROM
- Well first I want to thanks again for the ideas Jens Doll, Kyrylo Mikos and PA gave us on 4.3 allready to make our own SlimPie possible. We used partly code from them and added and changed it in our Slim way to have it for us most usefull.
- Well as known SlimPie advantage to other PIEs is that it can bind on every button press and longpress action like the user want. All SlimActions are available for every button (so all possible shortcuts we have + apps etc). Of course as well available are custom icon images or system icons. Other unique thing of SlimPie is that 2 rows are available. First row user can setup up to 5 buttons. On the second row up to 7 Buttons.
- Of course the user can setup the style to their like and still theme engine related things are respected.
- Pie is activated present on non expanded Desktop as well
- For 4.4 we reworked a lot of the frameworks base code mainly. Changes compared to 4.3
- We use now a edge detection service (thanks a ton to Jens and Kyrylo). We tweaked it only very minor due that it works allready out of the box. Two reasons why we want to use it.
1. We do not have detection overlays on the borders anymore. Means the user is not disturbed by it and we do not need to add workarounds like we did before to avoid accidental swipe ups (eg old IME reduce triggers). As well it is not needed anymore that the user can setup thikness etc. The default values are allready quiet good. If a device has detection problems the dm can adjust them via overlay. As said main main main advantage that no dead zones are present
anymore.
2. we will use this service for other upcomming features as well (eg new Recents)
- Centralized and adapted the code to 4.4 and some changes we did in our central classes
- reduced observer to an absolutly minimum. If PIE is disabled it does not observe any value
- A lot small fixes and tweaks
- Change default colors to KK style
- If navbar is present the navbar gets animated with the background to give a full screen overlay
feeling to the user. Especially now with kk transparency way better.
- Full keyguard support
- complete reworked edge disable detection
- and a lot more
Add "ActiveDisplay (rework interface)" - OmniROM
- really fix AD buggy stuff
- tested with Music play
- tested with No lockscreen
- tested with faster screen turn off
- check all sensor going off if AD not Showing or Disabled
- fix notification posted/removed
- make AD using System Window so it will covered all screen
- fix Navbar translucent if Lockscreen Blur merged :P
- now using Rounded Image
- also introduce new RoundedImageView widget
- courtesy of @vinc3m1 (thanks)
Settings: Fix PG Showing Duplicate SMS
- Clarify the SMS permission split for Read & Write from Send/Receive
Settings: Don't hide home category if user has a settings capable lanncher
- By default the settings app hides the home category if it notices the user
has 1 launcher. Due to the ability to have settings per launcher, if the
user only has one launcher which happens to support settings, hiding this
category renders that feature useless.
- So now we check if the user has < 2 launchers AND whether they support
a settings panel.
Settings: Create Omni audio theme's SoundPacks folder if necessary
Settings: Fix QS unsupported options are shown if called from outside
Settings + frameworks: Add user protection and pie/navbar toggle to Temasek Actions
- Slim original is SlimActions, renamed as Temasek Actions in temasek build
- Add drawables for it and enable it for navbar, pie, hwkeys
and GlobalMenu and whatever other shorcutfeature want to have it
Keep the user save and do not allow to disable all navigations to keep
the device usable. User will be notified
- In Settings user get the choice to enable the other navigation method. Of course only on navbar devices due that hw key devices always have a working navigation
Settings: Add Temasek Actions to Shortcuts
Settings: Fix Potential NPE in QS
OmniSwitch: service life-cycle tweaks
- Service must no be killed
frameworks/base: Add MORE smoothness (again). Feel the difference :p
frameworks/base: Addition of automobile profile and group apps
Additions
- An automobile profile to improve the OOB experience
- New apps to the profile groups...Google Calendar, Google Hangouts
frameworks/base: Revert "Frameworks: Add Fast Charge QS Tile"
frameworks/base: Add EdgeGesture service.
- Needed for SlimPIE
frameworks/base: fix qs and notification shade toggle on expanded desktop
- If expanded desktop is enabled and statusbar hidden the toggle does not force
the statusbar to show before it pulls down the shade
- fix it with just requesting the the statusbar to show up before we actually
peform the action
frameworks/base: Imagehelper...do a nicer resize with better quality
frameworks/base: BroadcastQueue: fix class typo of next receiver
- nextReceiver should be cast to ResolveInfo instead of ActivityInfo since it's ResolveInfo that is pushed into List r.receivers. Otherwise nextReceiver will always be null as there is no ActivityInfo in r.receivers.
frameworks/base: Make sure to turn off led after pulse()
- setLightLocked() will update mColor. This will cause the led to not be turned off after the pulse. When notificationManager starts a attention pulse the led will be kept on. Since attention is of highest prio nothing can turn it off. This is fixed by resetting mColor back to 0 after the call.
frameworks/base: fix navbar and pie icons for tablets and RTL
- well due that we use a completly other attempt then googles navbar we do not
need to rely on different sized icons for portrait and landscape. So just a square
icon fits our needs perfect (which is so or so everwhere in AOSP default to use square ones).
- Whatever recents pie feature showed us that we still forgot to size the pictures for our tablets and as well for RTL user.
- So let us do it now to fix any resizing issues on navbar and or SlimPie
frameworks/base: clean up the AOSP tablet icon mess
- well.....on grouper the overlay size for the navbar is/was 56dp...so google added bigger icons then the usual ones into the sw600dp folders. Well newer tablets have 48dp as default like the phones so the slightly bigger icons do not fit 100% correct. It is not much but it is noticable.
- So all devices have same navbar default height...so all icons should have same size as well. Just remove the overlay icons so that the system automatically chooses the right one from the default screen qualifier.
MMS: Enter key: force newline
- Provide an option to force newline (instead of send).
- For some keyboards (eg. SwiftKey) the shift+enter solution doesn't work.
Mms: Add Text Area Size preference
- This commits add the ability to set the size of the editable text are for composing messages.
Arbitrary Restrictions:
Min Limit - 2
Max Limit - 15
Updated cm source
11-02-14, 13:23
satoshi
Quote:
Originariamente inviato da Il Burocrate
CHANGELOG FOR V44.1
- For i9300 users who's last buld was V43 and now this build is V45.
Spoiler:
Added "SlimPie" - SlimROM
- Well first I want to thanks again for the ideas Jens Doll, Kyrylo Mikos and PA gave us on 4.3 allready to make our own SlimPie possible. We used partly code from them and added and changed it in our Slim way to have it for us most usefull.
- Well as known SlimPie advantage to other PIEs is that it can bind on every button press and longpress action like the user want. All SlimActions are available for every button (so all possible shortcuts we have + apps etc). Of course as well available are custom icon images or system icons. Other unique thing of SlimPie is that 2 rows are available. First row user can setup up to 5 buttons. On the second row up to 7 Buttons.
- Of course the user can setup the style to their like and still theme engine related things are respected.
- Pie is activated present on non expanded Desktop as well
- For 4.4 we reworked a lot of the frameworks base code mainly. Changes compared to 4.3
- We use now a edge detection service (thanks a ton to Jens and Kyrylo). We tweaked it only very minor due that it works allready out of the box. Two reasons why we want to use it.
1. We do not have detection overlays on the borders anymore. Means the user is not disturbed by it and we do not need to add workarounds like we did before to avoid accidental swipe ups (eg old IME reduce triggers). As well it is not needed anymore that the user can setup thikness etc. The default values are allready quiet good. If a device has detection problems the dm can adjust them via overlay. As said main main main advantage that no dead zones are present
anymore.
2. we will use this service for other upcomming features as well (eg new Recents)
- Centralized and adapted the code to 4.4 and some changes we did in our central classes
- reduced observer to an absolutly minimum. If PIE is disabled it does not observe any value
- A lot small fixes and tweaks
- Change default colors to KK style
- If navbar is present the navbar gets animated with the background to give a full screen overlay
feeling to the user. Especially now with kk transparency way better.
- Full keyguard support
- complete reworked edge disable detection
- and a lot more
Add "ActiveDisplay (rework interface)" - OmniROM
- really fix AD buggy stuff
- tested with Music play
- tested with No lockscreen
- tested with faster screen turn off
- check all sensor going off if AD not Showing or Disabled
- fix notification posted/removed
- make AD using System Window so it will covered all screen
- fix Navbar translucent if Lockscreen Blur merged :P
- now using Rounded Image
- also introduce new RoundedImageView widget
- courtesy of @vinc3m1 (thanks)
Settings: Fix PG Showing Duplicate SMS
- Clarify the SMS permission split for Read & Write from Send/Receive
Settings: Don't hide home category if user has a settings capable lanncher
- By default the settings app hides the home category if it notices the user
has 1 launcher. Due to the ability to have settings per launcher, if the
user only has one launcher which happens to support settings, hiding this
category renders that feature useless.
- So now we check if the user has < 2 launchers AND whether they support
a settings panel.
Settings: Create Omni audio theme's SoundPacks folder if necessary
Settings: Fix QS unsupported options are shown if called from outside
Settings + frameworks: Add user protection and pie/navbar toggle to Temasek Actions
- Slim original is SlimActions, renamed as Temasek Actions in temasek build
- Add drawables for it and enable it for navbar, pie, hwkeys
and GlobalMenu and whatever other shorcutfeature want to have it
Keep the user save and do not allow to disable all navigations to keep
the device usable. User will be notified
- In Settings user get the choice to enable the other navigation method. Of course only on navbar devices due that hw key devices always have a working navigation
Settings: Add Temasek Actions to Shortcuts
Settings: Fix Potential NPE in QS
OmniSwitch: service life-cycle tweaks
- Service must no be killed
frameworks/base: Add MORE smoothness (again). Feel the difference :p
frameworks/base: Addition of automobile profile and group apps
Additions
- An automobile profile to improve the OOB experience
- New apps to the profile groups...Google Calendar, Google Hangouts
frameworks/base: Revert "Frameworks: Add Fast Charge QS Tile"
frameworks/base: Add EdgeGesture service.
- Needed for SlimPIE
frameworks/base: fix qs and notification shade toggle on expanded desktop
- If expanded desktop is enabled and statusbar hidden the toggle does not force
the statusbar to show before it pulls down the shade
- fix it with just requesting the the statusbar to show up before we actually
peform the action
frameworks/base: Imagehelper...do a nicer resize with better quality
frameworks/base: BroadcastQueue: fix class typo of next receiver
- nextReceiver should be cast to ResolveInfo instead of ActivityInfo since it's ResolveInfo that is pushed into List r.receivers. Otherwise nextReceiver will always be null as there is no ActivityInfo in r.receivers.
frameworks/base: Make sure to turn off led after pulse()
- setLightLocked() will update mColor. This will cause the led to not be turned off after the pulse. When notificationManager starts a attention pulse the led will be kept on. Since attention is of highest prio nothing can turn it off. This is fixed by resetting mColor back to 0 after the call.
frameworks/base: fix navbar and pie icons for tablets and RTL
- well due that we use a completly other attempt then googles navbar we do not
need to rely on different sized icons for portrait and landscape. So just a square
icon fits our needs perfect (which is so or so everwhere in AOSP default to use square ones).
- Whatever recents pie feature showed us that we still forgot to size the pictures for our tablets and as well for RTL user.
- So let us do it now to fix any resizing issues on navbar and or SlimPie
frameworks/base: clean up the AOSP tablet icon mess
- well.....on grouper the overlay size for the navbar is/was 56dp...so google added bigger icons then the usual ones into the sw600dp folders. Well newer tablets have 48dp as default like the phones so the slightly bigger icons do not fit 100% correct. It is not much but it is noticable.
- So all devices have same navbar default height...so all icons should have same size as well. Just remove the overlay icons so that the system automatically chooses the right one from the default screen qualifier.
MMS: Enter key: force newline
- Provide an option to force newline (instead of send).
- For some keyboards (eg. SwiftKey) the shift+enter solution doesn't work.
Mms: Add Text Area Size preference
- This commits add the ability to set the size of the editable text are for composing messages.
Arbitrary Restrictions:
Min Limit - 2
Max Limit - 15
Updated cm source
Ma che senso ha parlate della 44.1 che nel post sopra ci sta la 45? ;)
11-02-14, 13:25
criiistian
penso perche nel changelog della 45 ci stanno solo le modifiche dalla 45 alla 44.1
cosi' si vede cosa e' cambiato dalla 44.1 alla 43
11-02-14, 14:31
Il Burocrate
Quote:
Originariamente inviato da satoshi
Ma che senso ha parlate della 44.1 che nel post sopra ci sta la 45? ;)
Ehm..l'ha spiegato temasek ;) "For i9300 users who's last buld was V43 and now this build is V45."
Quote:
Originariamente inviato da criiistian
penso perche nel changelog della 45 ci stanno solo le modifiche dalla 45 alla 44.1
cosi' si vede cosa e' cambiato dalla 44.1 alla 43
appunto
11-02-14, 23:49
pipolo0
Dopo svariati tentativi con la V43-44.1 con la V45 al 2° tentativo è andata, come detto alcuni post fà la 43 mi falliva stamani ho provato con la 44.1 scaricata diverse volte ma niente sempre Failed con l'uscita della V45 al 3° tentativo è andata mistero