PGP Support for BlackBerry Update
Hi,
Are there any plans, dates or details for an update to the PGP Support for Blackberry package?
Also, what is the process for logging & tracking feature requests relating to this package?
The particular feature we desperately want to see is:
To give a user the ability to send an encrypted e-mail with attachments from a BlackBerry device that is operating the PGP Support for BlackBerry package.
Currently the package can receive (decrypt) emails with attachments and only send (encrypt) emails without attachments. There is no workaround for this and it is a mayor limitation of the PGP Support for BlackBerry package. It is holding back the package from being rolled out to a larger market audience, and limiting existing users tremendously.
This feature request has now been logged with Symantec:
https://www-secure.symantec.com/connect/ideas/pgp-support-blackberry-encrypted-e-mail-attachments
and emailed to [email protected]
Any advice, comments or thoughts are welcomed.
Thanks,
I too would love to see this update! I feel most of RIM's resources are probably being put into getting BB 10 and infrastructure ready for launch?
My workaround for this issue is to install the SMIME support package and have users send encrypted attachments via SMIME. PGP support package has been updated to work with the SMIME package (to a degree). It automatically looks up certificates attached to the PGP users keys and encrypts and decrypts based on those public/private certificates.
Unfortunely the SMIME package isnt as user friendly, users contantly have to hit the blackberry button and then more or more all to load the entire message for longer messages and messages with attachments.
So far I can't seem to get AES Encryption working with the SMIME support package, only have managed to get 3DES and a few other inferior encryption algoriths to work with the SMIME package.
Similar Messages
-
Which frame works will support for blackberry application developement.
Hi
Which frame works will support for blackberry application developement?
Thanks
Achyuthello,
I think you'll have much more answers if you post in one of the three discussion boards "Blackberry Development" :
http://supportforums.blackberry.com/rim?category.id=BlackBerryDevelopment
Anyways, RIM has a website for people who want to start developing, it's here :
http://na.blackberry.com/eng/developers/started/
The search box on top-right of this page is your true friend, and the public Knowledge Base too: -
Where is Support for Windows Update issues for Windows Server?
Where is Support for Windows Update Issues for Windows Server?
Windows Update keeps prompting to install an important update, KB2871690 and continually fails with error code 0x800f922
I ran all the fixes I can find, it still fails.
I also tried the manual install, fails.
Microsoft used to provide no charge support for Windows Update issues. They additionally offer online fixes for other versions of windows, but not server, and I can't find a forum.
I also cannot ignore the update, it continually prompts.
I ran the windowsupdate.diagcab and it continually states it fixes Windows Update error 0x80070057, by resetting windows update data store. It further states it fixes Problems installing recent updates.
But it doesn't. I've run it 50 times, and it says the same thing every time.
So there is no support for windows update, and no support for windowsupdate.diagcab.
What's the deal?I've done the SFC/ SCANNOW and DISM
here is the cbs.log
What are we looking for?
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~BT\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360'. -
CDISMManager::put_ScratchDir
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$Windows.~BT\sources" - CDISMManager::LoadLocalImageSession
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM.EXE:
2013-12-04 19:48:20, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2013-12-04 19:48:20, Info DISM DISM.EXE:
2013-12-04 19:48:20, Info DISM DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
2013-12-04 19:48:20, Info DISM DISM.EXE: Dism.exe version: 6.2.9200.16384
2013-12-04 19:48:20, Info DISM DISM.EXE: Executing command line: X:\$Windows.~BT\sources\dism.exe /logpath:X:\$Windows.~BT\sources\Panther\cbs.log
/scratchdir:X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360 /image:X:\ /is-serviceable
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\FolderProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\FolderProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\WimProvider.dll -
CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\VHDProvider.dll -
CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\ImagingProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\ImagingProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\CompatProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\CompatProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2013-12-04 19:48:20, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2013-12-04 19:48:20, Warning DISM DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll
and wimserv.exe are up to date.
2013-12-04 19:48:20, Warning DISM DISM.EXE: Failed to add any commands.
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 physical location path: X:\ - CDISMManager::CreateImageSession
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Copying DISM from "X:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD"
- CDISMManager::LoadRemoteImageSession
2013-12-04 19:48:20, Info DISM DISM Image Session: PID=1644 TID=1656 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM OS Provider: PID=1644 TID=1656 Defaulting SystemPath to X:\ - CDISMOSServiceManager::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM OS Provider: PID=1644 TID=1656 Defaulting Windows folder to X:\Windows - CDISMOSServiceManager::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Manager: PID=1612 TID=1616 Image session successfully loaded from the temporary location: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD
- CDISMManager::CreateImageSession
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting Provider OSServices - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM OS Provider: PID=1644 TID=1656 Setting SystemPath to X:\ - CDISMOSServiceManager::SetSystemPath
2013-12-04 19:48:22, Info DISM DISM.EXE: Target image information: OS Version=6.2.9200.16384, Image architecture=amd64
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting the collection of providers from an image provider store type. -
CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM OS Provider: PID=1644 TID=1656 Get the registry path to the SOFTWARE hive located at X:\Windows\system32\config\SOFTWARE
and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
2013-12-04 19:48:22, Info DISM DISM Driver Manager: PID=1644 TID=1656 Further logs for driver related operations can be found in the target operating
system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Current image session is [OFFLINE] - CTransmogManager::GetMode
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Determined WinDir path = [X:\Windows] - CTransmogManager::GetWinDirPath
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Product Type: [ServerNT] - CTransmogManager::Initialize
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2013-12-04 19:48:22, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1672 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1672 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Processing the top level command token(is-serviceable). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the PE Provider. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Package Manager: PID=1644 TID=1672 Finalizing CBS core. - CDISMPackageManager::Finalize
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM OS Provider: PID=1644 TID=1672 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2013-12-04 19:48:24, Info DISM DISM.EXE:
2013-12-04 19:48:24, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2013-12-04 19:48:24, Info DISM DISM.EXE:
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider -
Does anyone know whether OCFO 10 provides improved support for Blackberry Desktop Manager? The previous version only supported up to version 3.6 (without SP1 or SP2).
Thank you.Hello,
The question is really one for RIM. So far, the Intellisync fixes have not been implemented in the Blackberry Desktop releases so you'll have to continue to run it against version 3.6.0 or earlier. The architecture changes to OCFO that will help circumvent this problem will not be available until mid-2006.
For over-the-air wireless synchronization, we have a number of great solutions for you. Through our partnership with Consilient, we can offer Blackberry-Oracle synchronization, and we'll soon be offering a push-IMAP solution for email that will work even better. You should talk to your Oracle Account Manager for more information about those solutions.
Hope that helps,
--Marc -
Support for Blackberry Browser to access applications?
Has anyone heard whether Oracle will begin to support Blackberry Browsers (i.e. 3G) for their web browser to access applications like I-expense or i-procurement?
Hi,
Please refer to the following documents.
Note: 458549.1 - Will iProcurement Work On A Blackberry?
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=458549.1
Note: 556634.1 - Is OAM Supported For Blackberry Devices?
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=556634.1
Regards,
Hussein -
No Direct support for BlackBerry PlayBook tablet - why not I just bought it?
I've just bought a playbook. It says it comes with complimentary technical support for 90 days form the date of purchase. I have attempted to register the device using the S/N number as required and I get the following:
Unfortunately, your BlackBerry® PlayBook™ tablet does not qualify for Complimentary Support. You can, however, get assistance using incident based support from Research In Motion.
Why? grrrrrrrrrrrrIt should be. The complimentary support is just for help setting it up.
If you visit http://blackberry.com/support and follow the link for PlayBook you should get a phone number you can call, and RIM support will be able to help you.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you! -
With the news of Blackberry's issues how long will they support the Z10?
I cannot speak for BlackBerry but I'm sure they will be around to support the millions of devices they have out there. They're down but not out.
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you! -
Slovak Telekom 4G/LTE support for BlackBerry Q10
Hello,
last month my carrier Slovak Telekom launched 4G/LTE network in our country (www.telekom.sk/english/press-center/press-releases/slovak-telekom-launches-first-nationwide-4g-lte-n... I would like to use my BB Q10 (SQN100-3) in 4G network, but my Q10 is not supported yet (in network mode 4G is missing). When will be Q10 supported? From what/who does the 4G/LTE functionality depend? From mobile carrier or BlackBerry?
Thanks
Kalliopp
Solved!
Go to Solution.Hi Julobaco,
you are right Q10 supports all Slovak frequencies you mentioned. There was not a problem with supporting frequencies. There was the problem, that LTE setting was disabled in the Network mode before May 2014. Thanks to the latest OS update 10.2.1.3175 released during end of May 2014 is LTE already enabled in the Network mode menu. Slovak Telekom LTE is available from November 2013. It means I was not able to use Slovak Telekom LTE for 6-7 months due to disabled LTE capability in the Network menu with Slovak Telekom SIM card on my Q10. I think it is very long time for waiting to a carrier update. It is finally ok -
Language support for blackberry maps
Hi,
Can the data on the blackberry maps be rendered in diffrent languages??
ThanksHey Rusty1007,
Welcome to the BlackBerry Support Community Forums.
Check out this article on how to install the East Asian
language pack on the BlackBerry smartphone:
http://www.blackberry.com/btsc/kb17208
I hope this helps,
Cheers!
-HB
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)! -
CUMA Support for BlackBerry KEPLER 9300 and BlackBerry BOLD 9780 models
Hi Community,
Does anyone has any information if Blackberry KEPLER 9300 and BOLD 9780 models are supported by Cisco Mobility Advantage?
Thanks in advance.Hi,
Right now CUMA doesnt support both these devices of Blackberry,
However you can find the list of Balckberry devices which is supported by CUMA in the following link:
http://www.cisco.com/en/US/docs/voice_ip_comm/cuma/CUMA_CUMC_Compatibility_Matrix.html#wp98582
Regards
Rajamani
P.S: Rate Helpful Posts -
Ukrainian language support for virtual keyboard
I'm very interested to be able to write in Ukrainian language on BlackBerry 10. However, the Ukrainian layout is missing. Thus, I created a new feature request which you can find here: https://www.blackberry.com/jira/browse/BBTEN-858.
If anybody else is also interested, please, follow the link and vote for it.
With best regards,
Oleksii Serdiukhobnob wrote:
leppa wrote:
Since reporting it on 14th of February it was assigned to someone on 21st of Ferbruary. No further updates or comments since then.
Any news on this at all? Any word from BlackBerry or elsewhere that Ukrainian will be included as a keyboard input option in future OS updates?
No news from my side but there's an article on ITC.ua which states that Ukrainian mobile operator MTS announced Ukrainian language support for BlackBerry 7 and 10 to be delivered by this summer. Not sure, however, whether it will be included in all ROMs or in some custom MTS one. Here's this article: http://itc.ua/news/smartfonyi-blackberry-poluchat-podderzhku-ukrainskogo-yazyika/
With best regards,
Oleksii Serdiuk -
Bengali language support for pearl 9105
Hi, I am using a factory unlocked blackberry pearl 9105 in Bangladesh. Regardless of my satisfaction with the device, it has become necessary for me to have my native language (Bengali) font for the device.
How can I have my device display Bengali fonts?Hi and Welcome to the Community!
Refer:
Article ID: KB05305 Localization support for BlackBerry smartphones
I'm not sure if the language you require is supported...but if it is, you can install it. If you need additional instructions for that, let us know.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
Twitter for BlackBerry 10 updated to v10.2.1.2
If you're a big user of Twitter for BlackBerry 10, then you'll be pleased to know that it has been updated. It's not my go to Twitter client but the updates lately have been pretty good and it is slowly becoming as good as it was on BlackBerry OS, at least for me. There is actually a changelog with this update and there are a handful of new features too.
What's new in Twitter for BlackBerry 10?
Lists! Lists are an easy way to keep track of accounts that Tweet about subjects relevant to your interests. You can now view, create, subscribe and edit Twitter lists from your BlackBerry device
Personalized trends surface and recommend accounts and conversations based on interests and locations
See more photos! Scroll through tweeted images in the photo image gallery
Learn more even more about fascinating peopl when you visit profiles. We now showcase other cool accounts to follow based on that person's profile you're viewing
New icon indicates Tweets with video!
DM status in app now syncs across all your devices and Twitter accounts
View recent Tweets while Twitter is minimized
That's a pretty nice addition of features. It certainly makes me want to use T4BB10 for a bit. If you don't see the update yet, try manually checking for updates. Alternatively, you could do a search for Twitter in BlackBerry World, that sometimes let's you see the update.
Download Twitter for BlackBerry 10 from BlackBerry World
Author: DJ Reyes / CrackBerry
Please thank those who help you by clicking the button.
If your issue has been solved, please resolve it by marking "Accept as Solution"josuefunes wrote:
If you're a big user of Twitter for BlackBerry 10, then you'll be pleased to know that it has been updated. It's not my go to Twitter client but the updates lately have been pretty good and it is slowly becoming as good as it was on BlackBerry OS, at least for me. There is actually a changelog with this update and there are a handful of new features too.
Are you still copy/pasting and plagarizing other peoples blog posts as your own, with no credit to the originating blog or author?
The author of this one happens to be a friend of mine...
You need to stop this. If you want to paste in this forum other people's work, please give the original authord AND the originating blog or website the credit for your pasted text and images.
It's just the right thing to do.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
Wanted to see what fixes or additions before updating.
Software updates are always exciting to experience FB2701. May I ask how did you receive the communication for this new update? The link for the available info on the blackberry update can be found in the link below.
http://www.verizonwireless.com/support/system_update/blackberryz30.html
Thank you...
ArnettH_VZW
Follow us on Twitter @VZWSupport -
I have a Curve 8300. With OS v4.5.0.81. And I am on a BB Social network plan through my cell providor "Fido".
I mainly use it for Facebook & Twitter and have no problems using either app. However I was prompted for an update for my twitter recently but wasn't near a wifi spot to update. Just decided to update today at home where I do have wifi. However when I go to do the update, it gives me the following error:
"Sorry your device does not meet the system requirements that are needed to support Twitter for BlackBerry Smartphones"
I have scoured for answers but haven't had much luck. I tried checking for OS updates. I apparently have the most current one that my phone will support. I uninstalled twitter and then tried to reinstall it via the twitter Icon on my phone. Got the same error. Tried reinstalling it through app world, it installed just fine. However it installed the version that I had previously had. So I went to twitter's settings and checked for updates. It prompted for one as I expected it would. And when I tried to get the update. It gave me that error again. I can use twitter as it is, but I don't see why my phone shouldn't be able to get all the updates for various apps. Is it a software compatability issue? Is it a hardware compatability issue? Is there anything I can do to get the update or do I just have a phone that won't take some app updates?Hi and welcome to the forums!
The 8300 is not listed in the device upgrade table for Blackberry device OS v5.0. The newer versions of apps like Twitter and Facebook require device OS v5.0 to run correctly. Might be time to consider a new device!
Thanks,
Bifocals
BlackBerry Device Software 5.0 main support page
Click Accept as Solution for posts that have solved your issue(s)!
Be sure to click Like! for those who have helped you.
Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.
Maybe you are looking for
-
How can I update my app on itunes 10.3 3
I just updated my itunes to the latest version, and I also want to update my apps, but I don't know how to do it in the new itunes..
-
I gifted a song not realizing the person had already purchased it on iTunes. If the person does not reedeem the song can I send either receive credit back or send another song?
-
T410 with 4337 docking station - can't get dual monitors to work
running win 7, unit has the Intel graphics. I can't figure out how to get any display to work off the docking station, VGA or digital. Discovery does not seem to pick up the external monitors.
-
CRM 2007 Upgrade - Std Comm. Method not visible in "More Fields"
Hi Gurus We recently upgraded from CRM 5.0 to CRM 2007. I'm verifying the Identify Account views, when I compare the "More Fields" view between CRM 5.0 and CRM 2007, the "Std Comm. Method field is not there. I though I could add this via configuratio
-
InDesign XML unparsed Entity unable to handle
Recently we switched over to the latest DocBook V5.1b2. This DTD includes entityref attribute whose required value is an ENTITY. Unfortunately this attributes throws error while validating in InDesign, which doesn't when validated with other XML vali