-
Notifications
You must be signed in to change notification settings - Fork 269
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
After testing with huge success we discovered here and there small problems (like NFC beam animation is broken, TRDS was disabled on cardock etc) which mainly was caused due that we used the already from AOSP introduced uiModes qualifier which could cause in special conditions this conflicts. Beside that we want a bit more flexibility. Result: This commit introduces the inverted qualifier as complete own qualifier undependent of the already AOSP used ones. Beside that it fixes all known issues......features: - it is now completly working over the AOSP Configuration classes Means every app get notice of a change trough onConfiguratioChange and restarts it's activity if change was detected. - app can disable that like some other configuration values over AndroidMainfest.xml - beside "inverted" folder another "notinverted" folder is introduced for another themeing (eg white) - qualifier order is direct before the official uiMode qualifiers (see AOSP docs) - All usual Configuration actions can be used with the inverted qualifiers....like BroadcastChange, direct read out from every app etc. etc. Note: Only system can change the uiInvertedMode So as you see a real own qualifier now NOTE: Apktool as well aapt need to be changed to fit the "new qualifier"....which means that we need to recompile our gapps that they react as well on this new behaviour. Think we will get them ready next 2 or 3 days. Patchset: increase support from SDK_HONEYCOMB_MR2 to FROYO to have better compatibillity to some gapps. Change-Id: I851740010198c400266d7ca9995eb08dbf7782bc
- Loading branch information
Showing
35 changed files
with
621 additions
and
119 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.