Why is installed application too big? - android

Yes i know there are similar questions but i couldnt see any problem there.
I analyzed it with Android Studio Tool
Installed on Android 6.0.1 and in Phone installed application it says ~42 MB?!?!
I have deleted some data there and it went down to ~16MB.
I dont understand why is it so big i dont have images or anything its just simple app with edittext that sums values.
PS. On android 4.2.2 it have ~4MB which is fair size.

Related

Complete utter wits end, all solutions online those not work for me for the Error "Session 'app': Error Installing APKs"

Utter Wits end. Tried all solutions: clean build, sync project files with gradle, build Bundles, Build APKs, disable and re-enable instant runs etc.
Followed Exact steps outlined in other threads/ posts but still couldn't get the app to run on my physical Samsung Galaxy S7 phone. It was working fine previously, but now couldn't get it to work. App still able to open on Emulators though.
Needed to test out gyroscope and accelerometer sensors on a physical phone which emulators can't achieve as intent.
Would like to seek help from the community regarding this matter. Any idea where it has gone wrong? I have already updated my compilesdkverison and targetsdkversion in the module:app build.gradle scripts. Tried almost everything that I can think of but to no avail. Hoping to see the light and receive enlightenment from the community as I'm a novice in Android Studio.
PS: By the way, how do people add actual iamges to the post, itseems like the only way i can show an image is in the form of a hyperlink away from current page. Is there a way to just put the image directly in the post here?
Looks like there is not enough space on your phone. Try making some space on your internal memory.

Each time I build my Android app (running on phone), I lose disk space

I've been developing an Android app for a week using Android Studio. I've noticed my disk space has been dropping and I don't know why. It seems that each time I run the app (99% of the time I use a test device, not an emulator), I lose disk space on my computer's hard drive. I have no idea why. Does anyone else know why and how I can fix it?
Update 2021: I had forgotten that I asked this question but someone else is having the same problem. I never figured this out on my old laptop. I ended up only working on my desktop (which didn't have this problem). Sorry I can't be more help :/
Try doing Build->Clean Project and then Build->Rebuild Project, it will reduce the space occupied by your project folder.
As for the rest, a good portion of the space occupied by Android Studio comes from the packages you have downloaded within the SDK manager. Try uninstalling those you don't currently need to free some space on your HD. See if it helps.

Android Layout resize and multiple emulations

I am going to create an app for devices with Android OS 2.1 and higher. As many developer I met layout problems and after reading about that in the official android documentation I decided to follow a way; I created 6 directory one for every screen density (ldpi,mdpi,hdpi,xhdpi,xxhdpi,xxxhdpi). What I want to know is if I did it right, I know that layout could be not exact at 100% but could I'll meet serious problems doing that?What I should do?
The second problem is checking app in many devices in the same time, I use Android Studio and I am able to create devices and use emulators but there is a plugin or a website or something else I can use to test quickly the app in tens of Android devices without set all manually?
Thanks in advance!

Corona sdk app runs great on emulator, but not when uploaded to Droid

I have been working a platforming game for about three months. I had the game working fine, and it worked fine on the Droid when uploaded. Recently, I worked on using director.class and a display group and navigating from the menu to the game using director:changeScene(). This works fine on the emulator with no error messages, but when uploaded to the Droid, the main menu loads just fine, but when I touch a button to load the lua file for the game, the screen goes black and nothing happens. I even un-installed several apps in case it was a memory problem, but that didn't change anything. Any help in what I am missing would be appreciated.
After much searching, I found the answer to my problem: The Corona emulator isn't case sensitive, but the Droid is case sensitive. I found that most of my .png files had uppercase extensions. As an example, pillar.png was actually pillar.PNG in the folder. Apparently, my graphic editor stores the file extension in uppercase by default. When viewing it with Windows Explorer, it wasn't obvious. I viewed them from the command prompt window and found the problem. Also any requires must be exactly the case as the filenames. After making this simple change, the apk deployed on the droid just fine. Also in my searching the forums, I found some other tips. The latest builds of Corona sdk have a problem with files stored in sub directories. Keep all your files in the same directory if you expect to deploy to a Droid.
Jerry
I had similar problem and thanks to #Jerry for pointing out images.
In my case image i included had resolution more than 2048 * 2048 (Maximum resolution allowed by Android as of now)
And reducing the image resolution solved the issue for me.
Kudos!!!

Android OsclNativeFile error: Seek lseek64 failed

I get the following error on my Android device:
E/OsclNativeFile( 1616): OsclNativeFile::Seek lseek64 failed
I want to know what it means, because I wasn't making anything special just getting a battery drain and the logcat show me zillion lines like the above. Thanks.
I got the same. That happened after i had updated my LG Optimus One P500 phone to android 2.3.3. I read this topic with no answers and was a bit disappointed. I tried to come back to 2.2, but phone didn't start (it stopped at android logo). I installed 2.3.3 again and it started normally. Then i experimented and soon noticed that there was no errors with sd-card unmounted. So I removed all programs from sd-card, and deleted all files from it (I moved it to laptop). And I have no such errors now. Maybe there is an easier way to solve it, but it has worked in my case.
The lseek64() system library function is typically used to access large files (2GB or greater). It's possible there's a flaw with the way the platform implements lseek64. A workaround--as tonixart has discovered--is to delete the large files on your sdcard.

Categories

Resources