Yoga 8 Update Kitkat auf Build A442_001_021 Verschlimmbesserung - Zensur hier im Forum

Hallo zusammen,
es ist doch kaum zu glauben, obwohl ich es erwartet habe...Unliebsame Threads werden wohl von Lenovo einfach gelöscht, also das altbewährte chinesische System...ZENSUR
Es ist eine Unverschämtheit, was sich Lenovo hier erlaubt. Kurz nach dem Update auf Kitkat 4.4. kam schon das erste Update auf das Build A442_001_021. Und wie ist das Ergebnis?
Katastrophal. Es hat sich bei den gravierenden Fehlern wie z.B. das Nichtfunktionieren von Google Maps und der drastisch reduzierten Performance gegenüber Jelly Bean 4.2 nichts geändert. Ferner lässt sich bekannterweise bei Kitkat die SD Karte bei ungerooteten Geräten nicht mehr korrekt benutzen...aber die braucht man ja laut Google eh nicht ;-))
Alle bekannten Fehler sind nach wie vor nicht behoben.
Und wenn man so etwas hier posted, wird der Beitrag einfach gelöscht...
Lenovo sollte sich bewusst werden, dass es mit so etwas keinen Kunden gewinnt. Im Gegenteil, so etwas verbreitet sich sehr, sehr schnell...
Aber wie schon in meinem von Lenovo gelöschten Thread erwähnt, lassen sich ja scheinbar unenendlich viele User all willfähige Beta Tester brauchen...
Denkt mal drüber nach ... Downgrade auf Jelly Bean 4.2 ist kein Problem (allerdings nicht mit Lenovo) 
Liebe Grüße an die anderen User hier im Forum...
M. aus G.

Duplizierte Beiträge werden unsichtbar gemacht, einen Beitrag der diesen dupliziert hat wurde wohl unsichtbar gemacht.
Andy  ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
  Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
PepperonI blog 

Similar Messages

  • How i can save report updation on report builder 10g

    how i can save report updating on report builder 10g
    please help me
    any help will be appreciated

    See anwer in :
    why no body try to help me its possible no body has idea about how to save

  • Any official Update for Flex Builder 3 to use Flash Player 10 Api?

    Any official Update for Flex Builder 3 to use Flash Player 10
    Api?
    How can i use flash player's 10 features in flex builder 3?
    Thanks

    I was able to solve my problem by modifying the solution
    offered in
    this
    technote.
    The technote identifies a permissions problem with the
    components directory of non-Safari browsers. In my case the
    permissions problem appears to have been in the main
    /Library/Internet Plug-Ins directory. What tipped me off to the
    solution was the fact that after manually removing Flash
    Player.plugin and flashplayer.xpt from the /Library/Internet
    Plug-Ins directory, subsequent attempts to install Flash Player
    resulted in the "Creating file: 1008:5, -5000 Access Denied Error"
    I remembered seeing in the technote. Before removing these files,
    the installer would just fail silently, perhaps because it saw
    files it was going to install already living in the right place,
    and furthermore had no permissions to alter the directory.
    In any case, by making the permissions change recommended in
    the technote to the /Library/Internet Plug-Ins directory, I was
    able to install the plug-in, which gave me back access to Flash
    content in all my browsers.
    Hope this is helpful to someone else...
    -Erik

  • [svn] 1636: update the framework build file we put in the sdk pkg.

    Revision: 1636
    Author: [email protected]
    Date: 2008-05-09 10:05:15 -0700 (Fri, 09 May 2008)
    Log Message:
    update the framework build file we put in the sdk pkg. I think this is probably going to go away, but I wanted to make sure it worked while it is still being put in.
    Modified Paths:
    flex/sdk/trunk/frameworks/build_framework.xml

    Hi Kevin,
    Dunno if you saw my other post to you, but I've put up a copy of the SDK that you were looking for and asked that we change our procedures going forward.  As for the actual issue, would you mind creating a bug report at bugbase.adobe.com if you haven't already?
    Thanks
    Chris

  • Updating Ad Hoc build with new Ad Hoc build does not preserve data

    Has anyone else had problems with an application losing its data when updated through a new Ad Hoc distribution and synced through iTunes? Both the old and new versions are Ad Hoc - I have already heard of the issues moving between App Store and Ad Hoc builds. I have searched a number of forums and have not been able to find any evidence either way. It seems most have had enough difficulty simply getting the Ad Hoc builds working.
    If anyone has experience updating Ad Hoc builds, your advice would be greatly appreciated.
    Kind regards
    Luke Gladding
    www.ledgerapp.com

    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Update new Folio Builder Panel but not the Folio Producer Tools?

    Hi Guys
    I was prompted to update the Builder Panel so I have done this now. I have read some older posts from last week about the new producer tools with new interactivity inside MSOs.
    Is everybody still having problems with this update or has the bug been fixed now?
    I'm not on such a tight deadline but I don't want any problems! Should I hold fire on updating the Producer tools?
    Cheers
    Gemma

    You can update the viewer builder panel independent from producer tools.
    So you can stay on version 17 of the tools but you need the current folio
    builder panel.
    —Johannes
    (mobil gesendet)
    Am 31.01.2012 12:47 schrieb "BHPforum" <[email protected]>:
       Update new Folio Builder Panel but not the Folio Producer Tools? created by
    BHPforum <http://forums.adobe.com/people/BHPforum> in *Digital Publishing
    Suite* - View the full discussion<http://forums.adobe.com/message/4175766#4175766>

  • About update the Folio Builder.

    In InDesign CS6, not able to update the Folio Builder. However, CS5.5, it is enabled.

    Download and install from http://www.adobe.com/downloads/ if the Help>Update in Indesign CS6 is not showing any updates for DPS Tools.

  • [svn:bz-3.x] 15191: Minor update to the build. xml and only make files write protected with chmod.

    Revision: 15191
    Revision: 15191
    Author:   [email protected]
    Date:     2010-04-01 07:06:21 -0700 (Thu, 01 Apr 2010)
    Log Message:
    Minor update to the build.xml and only make files write protected with chmod.
    Modified Paths:
        blazeds/branches/3.x/modules/sdk/build.xml

    DyNamic I agree that is sounds like you may be facing a network configuration issue.  Please let your network people know that you need access to the following servers and ports to download Adobe applications through the Adobe Application Manager:
    ccmdls.adobe.com:443
    ims-na1.adobelogin.com:443
    na1r.services.adobe.com:443
    prod-rel-ffc-ccm.oobesaas.adobe.com:443
    lm.licenses.adobe.com:443
    In addition for updates to download properly you will also need access to the following servers:
    http://www.adobe.com/:80
    htttp:///swupmf.adobe.com/:80
    http://swupdl.adobe.com/:80
    http://crl.adobe.com/:80

  • [svn] 3061: update the framework build. xml that gets included in the package

    Revision: 3061
    Author: [email protected]
    Date: 2008-09-02 12:38:17 -0700 (Tue, 02 Sep 2008)
    Log Message:
    update the framework build.xml that gets included in the package
    -use target-player = 10 for most frameworks
    -updated utilities target to use FlexContentHolder.swc and framework.swc
    Modified Paths:
    flex/sdk/trunk/frameworks/build_framework.xml

    The problem with re-using an existing WSUS is that ConfigMgr doesn't do anything with the existing approved and declenid updates. ConfigMgr will only use the metadata of the updates in WSUS. This could cause problems as the ConfigMgr client simply tells
    the WUA agent to scan against WSUS for compliance and then uses the update groups to tell the client which updates should be installed. In case the WUA agent finds updates directly on WSUS that are approved then it will also start to install those updates...
    That's why you should use one of them, as they will interfere with eachother..
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Lenovo Lynx K3011 Update Probleme auf Win 8.1

    Hallo Ihr Lieben,
    ich hoffe auf Eure Hilfe.
    Ich habe seit ein paar Tagen das Lenovo Lynx K3011 und habe sämtliche Updates gemacht auf frischem Windows 8....
    Problem a: nach runterladen und installieren sämtlicher Updates ( um die 100 Stück) fällt er in eine Schleife und will sich wieder zurücksetzten...
    Das heißt es sind alle Updates weg...
    Problem B: somit bekomme ich Win 8.1 nicht installiert.
    Gibt es die Möglichkeit eines Clean Install oder habe ich eine andere Möglichkeit?
    LG
    Bettsy
    Gelöst!
    Gehe zu Lösung.

    Hallo zusammen,
    wir haben den Kollegen aus der Technik einen Reminder geschrieben und hoffen auf ein Feedback...
    Sobald wir was von den Kollegen hören, melden wir uns.
    Danke und Gruß, Marcel
    → Wenn Du eine Lösung auf Deine Frage erhalten hast, markiere diese bitte als gelöst - Hilfreiche Beiträge verdienen Kudos. Zögere nicht Kudos zu vergeben.   

  • [svn:fx-trunk] 10505: Update to TLF Build 516.

    Revision: 10505
    Author:   [email protected]
    Date:     2009-09-22 10:35:30 -0700 (Tue, 22 Sep 2009)
    Log Message:
    Update to TLF Build 516. See textLayout/ReleaseNotes.txt.
    Updated build file so the manifest for textLayout_edit is removed since TLF did it with their build file.
    QE notes:
    Doc notes:
    Bugs:
    Reviewer: Gordon asked me to do this
    Tests run: checkintests, TextInput, TextArea, RichText
    Is noteworthy for integration: yes
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/textLayout/ReleaseNotes.txt
        flex/sdk/trunk/frameworks/projects/textLayout/build.xml
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/BaseTextLayoutImporter.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/HtmlExporter.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/HtmlImporter.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/TextConverter.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/TextLayoutImporter.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/manifest.xml
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/Build Info.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/BaseCompose.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/ComposeState.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/ParcelList.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/SimpleCompose.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/StandardFlowComposer.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/TextFlowLine.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/conta iner/ColumnState.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/conta iner/ContainerController.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/debug /Debugging.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/FlowElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/FlowGroupElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/FlowLeafElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/ParagraphElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/SpanElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/TCYElement.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/TextFlow.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/ITabStopFormat.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/ITextLayoutFormat.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TabStopFormat.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TabStopFormatInc.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TextLayoutFormat.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TextLayoutFormatInc.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TextLayoutFormatValueHolder.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/textLayout/EditC lasses.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/textLayout/edit/ SelectionManager.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/textLayout/opera tions/DeleteTextOperation.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/undo/UndoManager .as
        flex/sdk/trunk/frameworks/projects/textLayout/tlf.properties
    Removed Paths:
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkActiveFormat.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkHoverFormat.as
        flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkNormalFormat.as

  • Why "Announcement: iPhoto update 7.0.1 available now" in iPhoto '08 forum?

    Why is the "Announcement: iPhoto update 7.0.1 available now" in iPhoto '08 forum?

    good question.
    Here we have the iPhoto 08 forum. But if you look at the About iPhoto listing (iPhoto Menu -> About iPhoto), you'll see that what we have is iPhoto 08 (version 7).
    Clear? How about, iPhoto 08 is version 7 of iPhoto. See? That's not confusing in the least.
    But that's why the announcement is there.
    Regards
    TD

  • Air Auto Update Error -- Flash Builder Burrito.

    This is my first attempt at this, so I may be missing something simple.
    I'm not having any luck getting an Air app to automatically update.
    If I manually go to  http://localhost/air1/air1.air and redownload the file I will get a popup that asks if I want to update the app, but when I say ok I get this error.
    "There was an error checking for updates. Error# 16816"
    I haven't found a reason yet,
    Any ideas?
    update.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <version>2.0</version>
      <url>http://localhost/air1/air1.air</url>
      <description>1.0 - First version</description>
    </update>
    file -- air1.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx"
                           applicationComplete="init()">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Script>
            <![CDATA[
                import air.update.events.UpdateEvent;
                import air.update.ApplicationUpdaterUI;
                import mx.controls.Alert;
                protected var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI(); // Used for auto-update
                protected function init():void
                    // Check for update
                    this.checkUpdate();
                    Alert.show("checking update");
                // This function is triggered when the application finished loading.
                // Initialize appUpdater and set some properties
                protected function checkUpdate():void
                    // set the URL for the update.xml file
                    appUpdater.updateURL = "http://localhost/air1/update.xml";
                    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                    appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError);
                    // Hide the dialog asking for permission for checking for a new update.
                    // If you want to see it just leave the default value (or set true).
                    appUpdater.isCheckForUpdateVisible = true;
                    appUpdater.initialize();
                // Handler function triggered by the ApplicationUpdater.initialize.
                // The updater was initialized and it is ready to take commands.
                protected function onUpdate(event:UpdateEvent):void
                    // start the process of checking for a new update and to install
                    appUpdater.checkNow();
                // Handler function for error events triggered by the ApplicationUpdater.initialize
                protected function onUpdaterError(event:ErrorEvent):void
                    Alert.show(event.toString());
            ]]>
        </fx:Script>
        <s:Button x="47" y="55" label="Button"/>
        <mx:ColorPicker x="61" y="119"/>
        <s:ComboBox x="77" y="216"/>
        <s:ComboBox x="77" y="185"/>
        <s:ComboBox x="77" y="154"/>
    </s:WindowedApplication>
    file  -- air1-app.xml
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.5
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
        Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>air1</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>air1</filename>
        <!-- The name that is displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>air1</name>
        <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
        Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
        An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
        <versionNumber>2.0.0</versionNumber>
        <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
        <!-- <versionLabel></versionLabel> -->
        <!-- Description, displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        <autoOrients>false</autoOrients>
        <fullScreen>false</fullScreen>
        <visible>false</visible>
      </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
        specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image36x36></image36x36>
            <image48x48></image48x48>
            <image72x72></image72x72>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <!-- <customUpdateUI></customUpdateUI> -->
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
        <!--<android>
            <manifestAdditions>
            <![CDATA[
                <manifest android:installLocation="auto">
                    <uses-permission android:name="android.permission.INTERNET"/>
                    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                    <uses-configuration android:reqFiveWayNav="true"/>
                    <supports-screens android:normalScreens="true"/>
                    <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                    <application android:enabled="true">
                        <activity android:excludeFromRecents="false">
                            <intent-filter>
                                <action android:name="android.intent.action.MAIN"/>
                                <category android:name="android.intent.category.LAUNCHER"/>
                            </intent-filter>
                        </activity>
                    </application>
                </manifest>
            ]]>
            </manifestAdditions>
        </android> -->
        <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    This appears to be a Flex question. Please try posting to the Flex forums here http://forums.adobe.com/community/flex/flex_general_discussion for better response.

  • Properties not getting updated during dimension build

    Hi-
    I'm building an Account dimension. The build only updates the aggregation property and not the storage property. Any pointers at what can be the issue?
    I've a rule file that is set to allow property changes.
    thanks
    PARENT0,Account     CHILD0,Account     ALIAS0,Account     PROPERTY0,Account     PROPERTY0,Account
    AC_1     AC_2     Desc1     +     Dynamic Calc
    AC_1     AC_3     Desc2     +     Store
    AC_2     AC_2a     Desc3     +     Store

    Check out the link here: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotrules.htm
    Table 39. Member Property Codes shows the proper coding for properties. As far as I know, you need to use the codes instead of the store option names. S for store, X for dynamic calc, etc.
    Cheers,
    Mehmet

  • Updating to Flash Builder 4.6 plugin

    hi,
    I have FB 4.5(.1) as an Eclipse plugin. Now I want to upfate/upgrade to the 4.6 plugin.
    I read http://kb2.adobe.com/cps/921/cpsid_92180.html
    but it confuses me. So before I remove anything:
    I this a free update?
    If so, will the update recognize my serial key when I first uninstall 4.5?
    How about all the SDK's in my 4.5 sdks folder? Will I loose them?
    And hence, should I overlay again the AIR SDK after updating?
    thanks,
    Jeff.

    Thanks. It took me quite a while to get 4.6 installed.
    I uninstalled 4.5(.1) but got an error anyway when initializing the installation of 4.6
    Then I tried uninstalling Adobe Air from the utilities directory under Application as described in this thread
    http://forums.adobe.com/message/4088712
    That didn't work either.
    Finally I uninstalled Flash CS5 as well as my complete CS4 suite. I am not sure if only uninstallng Flash CS5 would have been sufficient, maybe.
    After this I sucesfully installed Flash Builder 4.6, and then re-installed the CS4 suite and Flash CS5.
    The only problem left is that when I create a new project and compile, I get a java.lang.NullPointerException
    but I will post that in a new thread...

Maybe you are looking for