Fix Parse Error – There is a Problem Parsing the Package
Fix 1: Check Your Apps Manifest File
This solution is only for the people who keep messing with apps Manifest file to make a modification to it. So, if you are one of them and made any changes to the Apps Androidmanifest.xml file then try restoring the file to its default state. Things you need to make sure to fix the parse error while installing an Android app:
The name of the .apk has been changed – So, if the original .apk was named as original.apk, and you renamed it to original1.apk then you may need to rename it to its original name that is “Original.apk”.
Once renamed, try to install the app on your Android phone and see if the parse error has been resolved.
The problem with your App’s code – Well, this isn’t something that I can troubleshoot and say what went wrong. But, if there is a problem with your code, you may need to look into that.
Fix 2: Allow Apps Installation from Unknown Sources
For the security reasons, the Android smartphone does not allow you to install apps from third-party sources or sources apart from the Google Play Store. Installing third-party apps from unknown sources can harm your Android phone.
So, if you are trying to install a .apk file then you may face the “parse error – there is an error parsing the package”. To fix this, what you can do here is allow app installation from the unknown sources. You can find the settings to the same under Security settings of your phone.
To allow app installation from the unknown sources, go to Settings and look for Security option under “Input and Control.”
Tap on Security and under Device administrators tap on “Unknown Sources, allows installation of apps from unknown sources”. If asked to confirm, tap OK.
Go back to the folder where you have the .apk located. Tap on it and install the app without parse error.
Fix 3: Enable USB Debugging
Enabling USB debugging isn’t really necessary for installing Android apps using the .apk file. But, for some users, enabling the USB debugging seems to have worked very well.
To enable USB debugging, you need to enable Developer Option in your Android phone first.
To enable “Developer option” go to, Settings, scroll down and tap on About Phone and then tap seven times on the “Build Number”. You should see a “You are now a developer” message on the screen.
Next, go to Settings again, scroll down and tap on Developer Options. Under developer options, tap on USB debugging and enable it.
The procedure to enable USB debugging for different devices will be different. There are dedicated websites such Enable USB Debugging with detailed instructions to do the same.
Fix 4: Disable Antivirus
The parse error can also occur if your security application is blocking the installation. Most of the Antivirus try to block the installation of the applications that may look untrusted or suspicious. So, if you are trying to install a .apk, the possibility is that your Antivirus app might be blocking the .apk file and preventing the installation.
So, try disabling the Antivirus temporarily and try to install the .apk file. This time, you should be able to install the .apk file without receiving any parse error in Android.
Fix 5: Corrupted APK or Partially Downloaded File
The phrase error – there is a problem parsing the package error can also occur due to a corrupted .apk file. Try downloading the fresh apk and install it. See if this can resolve the error. Also, make sure you download the complete file. Sometimes, you may partially download a .apk file and face Parse error while installing it.
Fix 6: Incompatible App
Some Android apps do not support the older version of the Android OS. Some apps do not support the older hardware of the smartphone. So, when you try to install an app which requires Android 4.4 KitKat above on an Android 4.3 Jelly Bean running smartphone then you will get “Parse error – there is a problem parsing the package” message. So, make sure you read the app description about the requirement on the Google Play Store.
Saturday, 6 May 2017
Saturday, 7 January 2017
How To: Create Instant FB & IG Poster
1) Goto PosterMyWall.com
Click CREATE A DESIGN button.
2) Create personal poster
2.1) Select Template
Select Blank Canvas.
2.2) Select Design Type
Select Instagram Post
2.3) Select Background Type
2.4) Edit Text
1. Add Text object.
2. Type Text content.
3. Set the Text Size and Text Alignment.
2.5) Add Clip Art.
Select Clipart/Add Clipart.
2.6) Place the Clipart on the Canvas.
Wednesday, 23 November 2016
As you can see from my results, the browsers were all surprisingly close to one another. The most interesting part for me was that Internet Explorer failed to load the object after the 250,000 record test. I couldn’t find anything pointing to a size limitation here. If anyone knows as to why IE failed to load the 500,000 record object, let me know.
Tuesday, 22 November 2016
Monday, 31 October 2016
Tethering is connecting one device to another. In the context of mobile phones and tablet computers, tethering allows sharing the Internet connection of the phone or tablet with other devices such as laptops. (https://en.wikipedia.org/wiki/Tethering)
HoRNDIS (pronounce: “horrendous”) is a driver for Mac OS X that allows you to use your Android phone's native USB tethering mode to get Internet access. It is known to work with Mac OS X versions 10.6.8 (Snow Leopard) through 10.12 (Yosemite – see notes below), and has been tested on a wide variety of phones. Although you should be careful with all drivers that you install on your computer, HoRNDIS has been tested at least well enough for the author (and many others) to run full time on their own personal computers.
HoRNDIS is implemented as a kext, rather than as a user-space program that opens a TAP or TUN device; this means that it does not conflict with other TAP/TUN kexts that you might have installed (like OpenVPN, Tunnelblick, or Cisco VPN). The driver implements Microsoft's proprietary RNDIS protocol, which is the only protocol supported natively by Android devices; although Linux and Windows users have enjoyed native RNDIS drivers for years, Mac OS X supports only CDC Ethernet devices out of the box.1)
The chief advantage of HoRNDIS over other tethering solutions is that it uses the a first-class supported feature in the phone's firmware. Other solutions either take over the phone's Wi-Fi stack without the Android operating system's knowledge, or create an emulation IP stack in userspace on the phone; in many cases, the built-in USB tethering support can be more stable, more reliable, and faster.2)
Downloading and installing HoRNDIS
HoRNDIS is available in source form from its project page on GitHub, and in binary form on this site. For quick start instructions:
Download the latest binary package, and double-click on it in your Downloads folder. Follow the instructions in the installer.
Assuming that the installation proceeds without errors, after it completes, connect your phone to your Mac by USB.
Enter the settings menu on your phone.
In the connections section, below Wi-Fi and Bluetooth, select “More...”.
Select “Tethering & portable hotspot”.
Check the “USB tethering” box. It should flash once, and then become solidly checked.
On some versions of OS X, a dialog box may pop up, prompting you to configure the device; follow its instructions. To verify that the device is connected, start the System Preferences program, and select “Network”; you should see your phone appear in the box at left. With any luck, you should be able to turn off Wi-Fi on your Mac, and browse the Internet through your phone's network connection.
The latest version available is release 8: HoRNDIS-rel8.pkg (78985 bytes) (md5sum 8991552bd384a06b7ec775f7198f7bba; GPG signature). Adds support for OS X 10.11 (El Capitan) and 10.12 (Sierra). Thanks also to David Ryskalczyk for his help in wrestling Xcode.
Release 7: HoRNDIS-rel7.pkg (116491 bytes) (md5sum 45a1a7457966b1dc79897af2864f68e4; GPG signature). Adds support for OS X 10.10 (Yosemite). Fixes issue where unsigned kext would not be installed (restoring support for OS X 10.6 - 10.8). Thanks also to David Ryskalczyk for his help in tracking down the issues with 10.10.
Release 6: HoRNDIS-rel6.pkg (116473 bytes) (md5sum fe3e5ae4c0a509b06cf11ef65b1715da; GPG signature). Adds support for multicast mode, enabling mDNS (thanks to Dan Yocom at Intel). Adds code signing support in Installer and for kext.
Release 5: HoRNDIS-rel5.pkg (60906 bytes) (md5sum 059164db5a76e5c0b57b9ef9acb65da5; GPG signature). Adds support for Mac OS X's Internet Connection Sharing, enabling BeagleBoard users to connect their boards to the Internet through their Macs.
Release 4: HoRNDIS-rel4.pkg (60519 bytes) (md5sum 8cf81024d8514d2a8654420fc7491b84; GPG signature). Actually fixes issue #5 and #9, adding support for Samsung Galaxy S II and HTC Desire S (thanks to Griskha). Improves compatibility with older versions of OS X (early 10.6).
Release 3: HoRNDIS-rel3.pkg (60488 bytes) (md5sum a46960e3cdb2a046e08af00c766b6ff9; GPG signature). Fixes issue #3 (reenabling installation on 32-bit machines). Adds potential fix for issue #5.
Release 2: HoRNDIS-rel2.pkg (60843 bytes) (md5sum 8b2c371e78ccfe3b07750fbe07f55bb5; GPG signature). Disables installation on 32-bit machines, and includes new device support.
Release 1: HoRNDIS-rel1.pkg (38681 bytes) (md5sum 4169c222448e2a2caaa067caf84189d3; GPG signature). Fixes issue #2.
Release 0: HoRNDIS-rel0.pkg (36807 bytes) (md5sum be4e879198d3b6e52af993b008198e8e; GPG signature). Initial release.
A special note about 32-bit machines
In previous versions, HoRNDIS required a 64-bit kernel. If you get an error message about 64-bit support on installing HoRNDIS, please try again with the version 3 package (or newer).
Notes about specific Mac OS X versions
OS X 10.9 (Mavericks) and 10.10 (Yosemite) are supported by HoRNDIS, but there are some gotchas. If you upgraded from an earlier version of OS X, you may find that phones appear to be replicating with abandon in your network control panel. If this happens to you, one somewhat heavy-handed workaround is to clean your network configuration files – take a backup of /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist and /Library/Preferences/SystemConfiguration/preferences.plist, and then either move them out of the way or delete them. (Note that this will remove any custom network configuration that you have performed!) I am still not sure what causes this problem, and so I do not yet have a workaround with finer granularity.
Versions of Mac OS X 10.11 and newer have a rewritten USB stack that is substantially less compatible than that in 10.10 and below. Unfortunately, Apple have not published any documentation for the new-style USB interfaces exposed in 10.11, so HoRNDIS can only use the USB APIs available in 10.10 and below, which have been broken in newer versions of OS X. As such, newer versions of OS X may have difficulty connecting to certain devices.
If, for some reason, you need to uninstall HoRNDIS, you can simply drag the extension to the trash. In the Finder, go to the “Go” menu, and select “Go to folder...”; in that, type ”/System/Library/Extensions”. Find “HoRNDIS.kext”, and drag it to the trash. When prompted, type your password. Do the same for the “HoRNDIS.kext” that lives in ”/Library/Extensions”, as well. Then, restart your Mac to be sure it is unloaded.
Getting and building the source
(Fork me on GitHub!) The source is available on GitHub; it is licensed under the GNU General Purpose License, version 3. To build the source, you'll need Xcode 4.0+ installed; to build a version that will work under Snow Leopard, you will also need the Snow Leopard SDK installed. Unfortunately, the Snow Leopard SDK is hard to come by nowadays; you'll need to find it somewhere on the web, and manually install it into your Xcode SDKs folder. (For most applications, it's OK to build against a newer SDK; for a kernel module, the magic vtable space-saving tricks require you to compile against the lowest common denominator.)
Simply running xcodebuild in the checkout directory should be sufficient to build the kext. If you wish to package it up, you can run make to assemble the package in the build/ directory (though please don't publish versions you built as if they were official!).
On the shoulders of giants, I stand. My vague thanks to Apple for having at least some IOKit sample code available (even though the last time it successfully built was 10.2.x); it was a decent start reading to understand how I might want to structure this. Substantial thanks to David Brownell, who wrote the rndis_host driver for Linux; some portions of HoRNDIS were ported over from that work. David Brownell also wrote the f_rndis driver that allows Android/Linux devices to behave like RNDIS devices; reading that source helped to understand why HoRNDIS wasn't working in the early stages. (Sadly, David Brownell passed away in April of 2011. Thanks for all of your hard work, David; may you rest in peace.)
Thanks also to those who helped test HoRNDIS before I released it, as well as all of the other folks from the days of the unrEVOked project, without whom I would likely not be involved in Android development at all...
Support and contact
And, after a tenure of three years, I am looking for a new maintainer for HoRNDIS. I no longer have the time to keep HoRNDIS up to date the way it deserves. If you believe that you have the skills to take on maintainership of this software, please let me know, or post in this GitHub issue.
Being free software, HoRNDIS comes with no warranty (not even a guarantee that it won't break your phone or computer! But I'm pretty sure it won't.), express or implied. (For more on that, read the license.) However, I hope that it works for you; if it doesn't, and you're able to assist in debugging, I'd like to hear from you.
So, for feedback, feel free to get in touch with me; especially if it works for you, or makes your life easier, I'd like to hear about it!
Wednesday, 5 October 2016
PROBLEM: Maya Outliner Window Is Missing.
SOLUTION: Refer Maya Troubleshooting Guide.