Been using this wallpaper program for almost a year now and for some reason keeps saying heap memory is to small. No clue what its talking about since its at 48m and always used to work. Wondering if anyone else is having this issue and knows how to fix it since comment's on the app seem all fine.
hey I need some help figuring this issue out. Why is my storage for applications all jacked up despite having over 5 gigs of space left?
Are you using any mods to move apps to your sdcard? It might be causing issues with the way the phone calculates the used space.
nope, I know it's a minor inconvenience but it just sucks that it isn't working right.
is there anyway to look up the app directory data files and see if any of those are larger than normal?
Recently I've been having a real bad experience with the Android Media Server, I know of the Rescan Media Server app that kills the service but that's not what I'm after. I know this problem plagues a lot of Android users and some might not even know that this is happening to their phones!
Is there a sure and permanent way to fix this problem? Like maybe an app to repair the corrupted files on the phone?
Formatting your SD card might help but with phones like the HTC One with non removable storage, having a corrupted file will be disastrous! I really hope Google will fix this issue :/
Hi, everyone.
You know, installing Apps if you're going to run out of space storage is a hard and big problem.
One of my classmates has got a low-end Galaxy Ace. And it's ONLY Got 180 MB Space Storage. That's horribly low - but the SD-Card has still 12 GB Free.
The app has a size of 4 MB.
So, how to install apps/apks directly to the SD-Card?
I hope to get an answer. Have a nice day.
Does Anyone?
...does anybody konw?
Hello,
I'm curious, has anyone has done any research into why, for some phones, using the SD card causes extremely severe degraded performance of the device? I realize there is a "Lag and sd card" thread, but most I'm looking more for developers input. Do any of the 5.1.1-based ROMs out there eliminate this lag? I am an experienced developer and although I'm not highly adept at embedded device kernel drivers I'm planning on taking a look there unless anyone has some general pointers on where else the issue may be.
All of the workarounds I've seen on this forum (reset/hard reset/full wipe/reflash/disable auto brightness/reformat SD card) have resulted in no help to narrow down the problem, so post away and let me know your thoughts!
Thanks
nbetcher said:
Hello,
I'm curious, has anyone has done any research into why, for some phones, using the SD card causes extremely severe degraded performance of the device? I realize there is a "Lag and sd card" thread, but most I'm looking more for developers input. Do any of the 5.1.1-based ROMs out there eliminate this lag? I am an experienced developer and although I'm not highly adept at embedded device kernel drivers I'm planning on taking a look there unless anyone has some general pointers on where else the issue may be.
All of the workarounds I've seen on this forum (reset/hard reset/full wipe/reflash/disable auto brightness/reformat SD card) have resulted in no help to narrow down the problem, so post away and let me know your thoughts!
Thanks
Click to expand...
Click to collapse
Right now I think the lag is based upon samsungs SD card implementation
Im using shinys kernel in my build
After I enabled full SD card permissions I'm am yet to see any lag but the occasion hiccups most of my users use sdcards so you should broaden what you are looking for. I think the better approach is to see in the lag and 5.1.1 thread those using stock kernel and stock rom vs etc...
Sent from my SM-G900T using Tapatalk
malbert16442 said:
Right now I think the lag is based upon samsungs SD card implementation
Im using shinys kernel in my build
After I enabled full SD card permissions I'm am yet to see any lag but the occasion hiccups most of my users use sdcards so you should broaden what you are looking for. I think the better approach is to see in the lag and 5.1.1 thread those using stock kernel and stock rom vs etc...
Click to expand...
Click to collapse
It may very well be in Samsung's implementation, but unfortunately that's not open source, at least from what I've found.
When you say, "full SD card permissions" what exactly does that entail? I am curious so I can extrapolate what you did to what might be affected.
Finally, do we know for sure if 5.0 also suffered from the same issue? I thought I recall it didn't... but my memory isn't that great sometimes.
5.0 doesnt have this issue
nbetcher said:
It may very well be in Samsung's implementation, but unfortunately that's not open source, at least from what I've found.
When you say, "full SD card permissions" what exactly does that entail? I am curious so I can extrapolate what you did to what might be affected.
Finally, do we know for sure if 5.0 also suffered from the same issue? I thought I recall it didn't... but my memory isn't that great sometimes.
Click to expand...
Click to collapse
My lag is memory based could be resolved my memory additions to build prop or some other methods of memory mangement
and also tweaking the autobightness in framework
I also disabled all animations for different task in framework under integers.
malbert16442 said:
My lag is memory based could be resolved my memory additions to build prop or some other methods of memory mangement
and also tweaking the autobightness in framework
I also disabled all animations for different task in framework under integers.
Click to expand...
Click to collapse
Define "memory additions" please. After some more research I am starting to agree, I believe it is memory based. I've largely noticed it seems to get triggered by Wifi and going out of range of a cell site (e.g. underground) or very weak signal. Yesterday I tried to reproduce the issue without those conditions and I could not. I was able to again reproduce them today by having Wifi on (not connected) and weak cell signal.
Once the issue occurred I dumped the kernel log (dmesg) and noticed that there are commands (e.g. ls and setprop) returning 'undefined instruction' at a particular memory address. One of the few ways this could happen is if the memory address is being overwritten or cleared.
Code:
<6>[14735.260878] ls (24699): undefined instruction: pc=b6e0cf48
<6>[14735.260886] Code: ea000002 00000000 f26ee1fe e12fff1e (ee190f1d)
<6>[14735.267542] setprop (24702): undefined instruction: pc=b6e8ef48
<6>[14735.267550] Code: ea000002 00000000 f26ee1fe e12fff1e (ee190f1d)
What would be valuable to know is if these messages are showing up for anyone else when they're not having the issue.
From the top of my head I recall there being a new version of the wifi driver (complete re-write) in 5.1.1. This might be the issue. For the nay-sayers that think Marshmellow won't fix the issue, there's actually a good chance it will since it'll likely have a refresh of the BCM module (wifi).
More investigation still is being done, however...
I assume memory additions refers to the JVM memory and other memory allocations? That could certainly affect the issue. Would be interesting to see the various memory related arguments in your build.prop.
I've continued to do some more research here and there and last night I found that there was a new buffer added into the wifi driver that allocates more memory than previous drivers. My next steps are to a.) validate that the memory pre-allocated is always sufficient to cover the max size of all buffers and b.) To adjust the buffer sizes and/or revert the new changes in the wifi driver regarding this new buffer.
Ill look into this
nbetcher said:
I assume memory additions refers to the JVM memory and other memory allocations? That could certainly affect the issue. Would be interesting to see the various memory related arguments in your build.prop.
I've continued to do some more research here and there and last night I found that there was a new buffer added into the wifi driver that allocates more memory than previous drivers. My next steps are to a.) validate that the memory pre-allocated is always sufficient to cover the max size of all buffers and b.) To adjust the buffer sizes and/or revert the new changes in the wifi driver regarding this new buffer.
Click to expand...
Click to collapse
@ShinySide any thoushts
malbert16442 said:
@ShinySide any thoushts
Click to expand...
Click to collapse
Since then I'm not entirely convinced that it's the wifi driver, but I haven't entirely ruled it out because turning Wifi off from Android doesn't actually unload the wifi driver itself.
I'm fully capable of fixing this issue, but what I'm really still lost on is finding out EXACTLY how to reproduce this issue. I spent half of Saturday trying to reproduce various ways with no success. If someone has any way of specifically reproducing the issue that would be of immense help.
I've found a way to reproduce the issue, at least with my phone. Basically whenever your cell connection is downgraded to HSPA+ (instead of LTE) the issue starts occurring the more time you're on HSPA+. I found this as the cause because at work we have a cell booster that boosts HSPA+, but not LTE, causing the HSPA+ signal to be preferred. At work the issue occurs all day long until I leave (where I get LTE) and the issue very quickly goes away. Now today at home I was briefly downgraded to HSPA+ and my phone started to slow down to a grinding halt. It's worth mentioning that I did re-flash the FOG radio last night, but the issue still happens.
Is anyone else able to reproduce this issue when on HSPA+? When downgraded to HSPA+ use a bit of data and see if it happens.