Tag: backup

In Windows 7, trying to do backup, getting error code 0x8078002A

had this problem, too, with Windows 7, trying to use Windows Backup to two new Western Digitial 3TB drives, pre-formatted with NTFS for Windows. It’s very frustrating because each attempt takes many hours before the error occurs so you don’t know until it succeeds whether it will.

I found what worked for me here:

http://wdc.custhelp.com/app/answers/detail/a_id/6618/

You can download WD Quick Formatter from that site. However, don’t follow the instructions on that page for formatting a HD under Windows 7, because it tells you how to use MS Disk Management, which will make a 2TB partition and not recognize the remainder of the drive. You must use WD Quick Formatter as described here:

http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868

Google provides quite a number of cases involving the same problem you are experiencing. None seemed to be resolved. A number refer to USB external drives.

My research has led me to the two sites mentioned below. On the Petri site I found the quotes extracted as they may point to a possible solution.

Are you using an Enterprise or Ultimate version of Windows as these include Bit Locker Drive Encryption

As a general recommendation in regard to using Windows 7 as a client operating system, use either internal hard disks, separate from the one Windows is installed on. Alternatively, use an external USB hard disk and make sure you disconnect it after you perform your backup.

You cannot use any of the following destinations:

•The destination is locked by BitLocker Drive Encryption.

Source:http://www.petri.co.il/where-to-save-your-windows-7-backup.htm

http://www.sevenforums.com/tutorials/4681-bitlocker-drive-encryption-windows-7-drive-turn-off-no-tpm.html

titanium backup cloud upload fails

I’m able to backup to Google Drive and Dropbox, but it’s a bit fragile. TB coding for the syncs/backups is really not very robust. The notifications are pretty nondescript and there is no real logging. It seems to me that any glitch in the data transfers cause the syncs to exit, rather than execute any retries.
I’m having some troubles too im on TBP 5.6 and whenever i sync to either drop or drive i get “upload to google drive failed network error”. However i dont need to resume, i can continue. Im not sure if those backups are viable since it was disconnected so many times. The backups work, but the code seems to me to be not very robust. You need to watch your notifications to make sure the backup was successful, and if not, run another one manually.

It’s annoying, and I don’t think it’s going to change.

Google Drive and Dropbox give network errors when trying to upload. I bought Titanium Backup Pro specifically for cloud sync. The first time, it synced about 300 MB to my Google Drive account, but then the backup stopped. Now it doesn’t even sync that much anymore; it just fails – BOTH on Google Drive and on Box. For Google Drive it tells me there was a “Network error”, for Box it tells me: “Internal error com.android.providers.settings.apk.lzop”

Try Foldersync.

Had some issues originally syncing to the cloud where it always failed and it turned out to be Google music related. Specifically I think it was the amount of offline files it couldn’t sync or maybe it was a database, I don’t recall but basically I setup a new job to sync very little and slowly increased it until I figured out what the issue was.

Delete the backup for the apk listed in the error message, then back the app up again. That’s fixed Dropbox sync issues for me on multiple occasions.

Android SDK

Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012[update], more than 700,000 applications have been developed for Android, with over 25 billion downloads.[2][3] A June 2011 research indicated that over 67% of mobile developers used the platform, at the time of publication.[4] In Q2 2012; around 105 million units of Android smartphones were shipped which acquires a total share of 68% in overall smartphones sale till Q2 2012.[5]

The ADT Bundle provides everything you need to start developing apps, including a version of the Eclipse IDE with built-in ADT (Android Developer Tools) to streamline your Android app development. If you haven’t already, go download the Android ADT Bundle. (If you downloaded the SDK Tools only, for use with an existing IDE, you should instead read Setting Up an Existing IDE.)

Install the SDK and Eclipse IDE

  1. Unpack the ZIP file (named adt-bundle-<os_platform>.zip) and save it to an appropriate location, such as a “Development” directory in your home directory.
  2. Open the adt-bundle-<os_platform>/eclipse/ directory and launch eclipse.

That’s it! The IDE is already loaded with the Android Developer Tools plugin and the SDK is ready to go. To start developing, read Building Your First App.

Caution: Do not move any of the files or directories from the adt-bundle-<os_platform> directory. If you move the eclipse or sdk directory, ADT will not be able to locate the SDK and you’ll need to manually update the ADT preferences.

Additional information

As you continue developing apps, you may need to install additional versions of Android for the emulator and other packages such as the library for Google Play In-app Billing. To install more packages, use the SDK Manager.

Everything you need to develop Android apps is on this web site, including design guidelines, developer training, API reference, and information about how you can distribute your app. For additional resources about developing and distributing your app, see the Developer Support Resources.

There is a community of open-source enthusiasts that build and share Android-based firmware with a number of customizations and additional features, such as FLAC lossless audio support and the ability to store downloaded applications on the microSD card.[42] This usually involves rooting the device. Rooting allows users root access to the operating system, enabling full control of the phone. In order to use custom firmwares the device’s bootloader must be unlocked. Rooting alone does not allow the flashing of custom firmware. Modified firmwares allow users of older phones to use applications available only on newer releases.[43]

Those firmware packages are updated frequently, incorporate elements of Android functionality that haven’t yet been officially released within a carrier-sanctioned firmware, and tend to have fewer limitations. CyanogenMod and OMFGB are examples of such firmware.

On 24 September 2009, Google issued a cease and desist letter[44] to the modder Cyanogen, citing issues with the re-distribution of Google’s closed-source applications[45] within the custom firmware. Even though most of Android OS is open source, phones come packaged with closed-source Google applications for functionality such as the Android Market and GPS navigation. Google has asserted that these applications can only be provided through approved distribution channels by licensed distributors. Cyanogen has complied with Google’s wishes and is continuing to distribute this mod without the proprietary software. He has provided a method to back up licensed Google applications during the mod’s install process and restore them when it is complete.[46]

The NDK is a toolset that allows you to implement parts of your app using native-code languages such as C and C++. For certain types of apps, this can be helpful so you can reuse existing code libraries written in these languages, but most apps do not need the Android NDK.

Before downloading the NDK, you should understand that the NDK will not benefit most apps. As a developer, you need to balance its benefits against its drawbacks. Notably, using native code on Android generally does not result in a noticable performance improvement, but it always increases your app complexity. In general, you should only use the NDK if it is essential to your app—never because you simply prefer to program in C/C++.

Typical good candidates for the NDK are self-contained, CPU-intensive operations that don’t allocate much memory, such as signal processing, physics simulation, and so on. When examining whether or not you should develop in native code, think about your requirements and see if the Android framework APIs provide the functionality that you need.

MobileGo is a life saver for those who love music and video, text a lot and juggle apps on their Android phones and tablets.

Android Fans:Backup everything to PC with 1 click & retain 100% quality.
Music Lovers:Instantly add fun stuff and enjoy media anytime, anywhere.
App Addicts:Download, install, uninstall and export apps quickly and easily.
Socialites:Transfer contacts from/to Outlook and send & reply SMS seamlessly from your PC.
The Android 3.1 platform (also backported to Android 2.3.4) introduces Android Open Accessory support, which allows external USB hardware (an Android USB accessory) to interact with an Android-powered device in a special “accessory” mode. When an Android-powered device is in accessory mode, the connected accessory acts as the USB host (powers the bus and enumerates devices) and the Android-powered device acts as the USB device. Android USB accessories are specifically designed to attach to Android-powered devices and adhere to a simple protocol (Android accessory protocol) that allows them to detect Android-powered devices that support accessory mode.[22]