Hi guys!
A month ago i made some optimization to my phone(including and supercharger script update). Now the phone is very fast, even now it doesn't suffer from music stutter after long stand-by(have that in mind the the cpu rendering is disabled and the gpu needs a lot of memory streaming, but its running fine). Some of the things i made were turning on to clean the VM every 12 minutes(or smth like that) and limitng the Dalvik size to 38MB from the build. Everything is running very well and fast(ohh, btw, im running .587), but the problem is when i stop to record video(longer than half minute), the camera freezes and it's unable to properly save the video(Cyber-Shot 2B.). Only saves amount of data with extension but with no header. Is it due to VM size, or the frequent VM cleaning or something else?
One other question, as far as i know, Dalvik starts after loading Kernel, OS and after starting initial services, but is it possible to set Dalvik limit depending on the processes runing? I'm not a programmer but i don't know how to say it, i've written something looking like a code to present what i mean. Thanks in advance!
#!/system/bin/sh
if 'pidof com.sonyericsson.android.camera' (i don't know what to code for cheking if the process is started).
then dalvik.vm.heapgrowthlimit=120m and dalvik.vm.heapsize=120m
else
dalvik.vm.heapgrowthlimit=38m and dalvik.vm.heapsize=38m;
sleep 10
while(1)
EDIT: I don't know if i've deleted the caches(dalvik and partition, but i'll give a try).
Related
Hello good people of XDA, I am having a bit of an annoying issue with my Cyanogenmod 7.1 "stable" install on my Evo 4G. Tiamat 4.1.0 SBC+ Kernel.
When I run a gps related application like Ulysse speedometer, Google Maps and Navigation, after a seemingly random amount of time the phone crashes and reboots itself. The time that I can use the app may be a few seconds to a few minutes and I havent noticed anything that would help determine the timing issue.
I have been doing a little testing and while running logcat on my PC via ADB, I have pulled the last events that occur immediately before the crash. It seems to me that the issue is more/only likely to occur when the phone is also not connected to a wifi network. Everything works fine when using GPS while connected over wifi.
Is anybody interested in reading through the end of my log file? How should I post it?
Please, any help at all?
sntmods said:
Please, any help at all?
Click to expand...
Click to collapse
I've been having the same problem as you and I think I've figured out a fix for it. I'm on Deck's 1.3 stable (which is essentially CM7.1) with Tiamat 4.1.0 SBC, using the smartass governor (the original one) with a CPU frequency range from 128 MHz to 768 MHz, and undervolted by 100 mV.
I've only encountered the issue sporadically and it's only occurred when using Google Maps or Navigation. I would be using Maps and moving the map around a lot, rotating it, or zooming in and out and all of a sudden the screen would freeze and the phone would reboot after 10 seconds or so. I figured out that I could reproduce the problem by opening up a bunch of apps to get the free memory (RAM) down to about 100 MB, open up Google Music and start streaming a song on the handset speaker, then open up Maps and just move around the map a lot; after less than a minute of doing this, the screen would freeze and the phone would reboot.
I tried uninstalling and reinstalling Maps; wiping the cache, dalvik cache, and fixing permissions; reverting to an older version of Maps (5.10); reversing the undervolting; changing governors; and changing the CPU frequency range; but none of these things fixed the problem.
I noticed that if I tried the Music and Maps crash technique when there was more free RAM (say 150 - 250 MB free), it wouldn't work, so I figured the problem probably had to do with the apps in use not having enough available RAM to operate properly and the default values that Android uses to kill idle apps was set too low. Fortunately, I remembered about Autokiller Memory Optimizer, which allows you to set those values, so that you always have above a certain level of free RAM. First, I tried the “Aggressive” preset (82, 90, 98), which didn’t fix the problem, so I then tried the “Extreme” preset (150, 160, 170) and that fixed it (for a full explanation of what the numbers mean and how the app works, see the Autokiller Memory Optimizer). I tried several different combinations of values between the Aggressive and Extreme presets and finally settled on Hidden app: 110, Content provider: 120, Empty app: 130. I was able to use lower values and still prevent the crash/reboot issue, but I figured I should leave a little buffer room to be safe and the 110, 120, 130 combo seemed low enough to prevent idle apps from being unnecessarily killed.
So, I’m not exactly sure what the root cause of the problem is, but Autokiller Memory Optimizer seems to be a nice workaround to fix the problem.
Well after testing this workaround for some time now, I can say that it doesn't prevent the reboots completely, but it does seem to have decreased their frequency, such that it's only happened one or two times since I started using it. I tried changing the cutoff values for when certain types of apps are killed, but eventually returned to the original levels I went with (Hidden app: 110, Content provider: 120, Empty app: 130) as they seemed to work the best (the one or two reboots that did happened, occurred when I was experimenting with the values).
Hi All,
I created this thread as I can't post at the developers section yet, however I noticed a huge battery drain after I flashed TermaROM and used DT A2SD, I never encountered this problem before when I was on a BancetDEV ROM using Link2SD (as BancetDEV DT A2SD is a buggy after installing several apps). I can also say that this applies to Creed's ROM when I tested it at version 2.1
Anyway, I got the same apps and widgets on my screen, wi-fi, data, 3G are all turned off, however I am losing battery so fast even at idle mode, whilst if I am playing music - using Player Pro - I am losing battery at average of 10 to 12% per hour, unlike before it was around 5 to 8%.
I am still investigating this and currently using better battery stats, however I hope anyone can also share experiences with battery drain on this ROM or maybe with DT A2SD overall.
Furthermore I already under-clock my CPU at 312 MHZ every time I turned off my screen, v6 supercharger, and definitely the battery is calibrated properly. I also searched the forum for possible answers but I can't find any nor in google lol or maybe I am just poor in searching for answers.
Additional Info: I know this is a hassle, however DT A2SD is better than link2sd, as link2sd got an issue w/ dalvik cache if your hoarding a lot of apps.
Update:
* I also got a battery level drop to 1% after reboot, but eventually it will go back to the correct value and battery level drop to 95-98% when disconnecting charger wherein its pretty normal so its not an issue, but maybe the level drop to 1% after reboot could be a related problem.
i think so too,battery drain when using A2SD by terma kernel
it might be...not sure thou..
but since you moved the app and data to ext..it takes more "juice" to retrieve them...specially if you have dalvik on ext too...
cause instead on the normal process..of android os retrieving data directly form phone it checks phone first and since no data on phone it checks ext..
then retrieccves it there...
unlike if no a2sd..
os-then phone back to os...
with a2sd
os-phone-ext-phone-os...
thanks for the reply guys, hope we can solve this issue or get an answer, by the way when I was using Player Pro it was installed in system memory not on sd-ext, including my widgets (battery widget monitor, system tuner), I look up at different post in here but I can't find anything in regard to DT A2SD excessive battery drain so it might be with the ROM itself?...
it depend in your memory card
ive got that battery drain too, overnight i sleep at 80% then after 6 hours it's 0%. then sometimes it just shut off itself. i stop using a2sd, my phone works just fine.
Via XDA App
be calm...thats totally normal. the system use a lot more power to read and run the app in the SD. thats the reason why your battery drain quickly when using this feature.
kurotsugi said:
be calm...thats totally normal. the system use a lot more power to read and run the app in the SD. thats the reason why your battery drain quickly when using this feature.
Click to expand...
Click to collapse
I also considered that aspect specifically in terms of reading / writing on the sd card, however even at idle mode it takes a lot of power? I just killed everything via android task manager, and running services doesn't state any third party apps running at this point, yet its still eating a lot of power....
eyjay1991 said:
ive got that battery drain too, overnight i sleep at 80% then after 6 hours it's 0%. then sometimes it just shut off itself. i stop using a2sd, my phone works just fine.
Via XDA App
Click to expand...
Click to collapse
thanks mate, guess I don't have a choice too lol, however its really weird as Link2SD doesn't take a lot of power, and as far as I know the only difference between A2SD and Link2SD is how they generated the symlink - as for symlink - Link2SD is creating a link for every item, whilst A2SD is creating a link for the whole folder itself (which might explain pulling up a single app takes a lot of power as its pulling up the whole folder that contains the app? lol)
Anyway the only advantage of A2SD is handling the dalvik cache and saving the hassle to relink dalvik cache during reboot.
EDIT: I apologize for double post
using a2sd script means you're not only move the 3rd party app to the sd. basicly you're also move all dalvik-cache in /data to your sdcard too. even you turn off your 3rd party app that doesn't mean you're not access your sdcard.
thanks for the reply guys, my phone got wipe out after testing different roms and a kernel that was being develop by someone here in xda, lol anyway guess its really eating a lot of resources on the background, although it can't be seen in the processes... hope we could have more answers soon
Lately my G4 has suddenly locked up several times, usually when unlocking. Everything would slow to a crawl (several minutes for anything to respond) or freeze entirely until I rebooted (which sometimes required pulling the battery).
I installed Cool Tool to diagnose the problem and found that it happens when free RAM gets under about 180MB. kswapd kicks in with several hundred MB/s of I/O (I saw it over 1000 once). I'm not sure what it's doing with that much I/O, but of course it makes everything grind to a screeching halt.
Looking in Kernel Adiutor (sic), ZRAM is set to 700MB and swappiness (who puts swap on a flash storage device anyway?) is 80. Both seem very high to me. Why using 700MB of precious RAM food for a virtual, compressed (slow!) swap file, and swap so often? I adjusted them to. 250MB and 20 respectively. As expected I now have way more free RAM (average ~600MB, up from ~300), things seem more responsive and I haven't had any lockup (but I only did this a few hours ago, so too early to know if it really fixed the problem).
Anyone know why these were set to such large numbers? Anyone else have this issue and if so, does this tweak help?
Mine was 40 in swappiness but zram value stick to 700mb
That's odd. I wonder if some process adjusts it on the fly when RAM is low?
Just had another "freeze" with ~200MB free. Again kswapd doing a bunch of I/O and slowing everything else down. Wasn't nearly as bad this time though. Less I/O going on, things were sluggish but not completely frozen, was able to open the recent apps menu and hit Clear All to free up a ton of memory and get things running smoothly again. Maybe need to tweak OOM killer and swappiness settings more so I don't have dozens of old aops/tabs hanging around hogging memory.
RenaKunisaki said:
Just had another "freeze" with ~200MB free. Again kswapd doing a bunch of I/O and slowing everything else down. Wasn't nearly as bad this time though. Less I/O going on, things were sluggish but not completely frozen, was able to open the recent apps menu and hit Clear All to free up a ton of memory and get things running smoothly again. Maybe need to tweak OOM killer and swappiness settings more so I don't have dozens of old aops/tabs hanging around hogging memory.
Click to expand...
Click to collapse
are we both the odd bunch? this is the first time I've come across someone else experiencing the same issues as me! switched from a Samsung to an LG, 3GB to 4GB device respectively, and still experiencing this from time to time.
From last few months, I've been noticing a major slow down in my device. It lags a lot freezes while opening almost any app making the phone almost unusable for daily basis. I don't know what's causing the slow down.
Here's what I've already tried with no positive results:
- Completely formatting SD card + Internal storage and Flashing stock ROM
- Completely formatting SD card + Internal storage and Flashing CM ROM with all android versions (4.1, 4.2, 4.3, 4.4, 5.0, 6.0)
- Frequently cleaning cache partition and wiping all application's cache.
I also have very few apps installed on my phone and there are no major load on the RAM as well.
I am wondering what can cause such slow down?
As far as I remember, this device wasn't that much slower when I first got it about 2 years back.
Does Google services are causing incompatibility with this device causing freezes or this is a hardware issue? (If it is, then which part of hardware could it be?).
Also do you also experience such slow downs, lags and freezing?
You can try to change your kernel and modify a few things. I really suggest using Wild Kernel and downloading the Trickster MOD app on Playstore and change your settings. I usually set my Governor to "ondemand" and it's worked pretty well. I used to have this problem too back when I had the phone on "batterysaver" and it was a mess.
I agree with the kernel tweaks. I"ve noticed that this device does NOT like to go below about 250mb free ram. I've set my LMK settings very aggressively. Accept for foreground applications, I've set everything to 3x normal.
I too am using On demand, tweaked.
I/O set to BFQ
I also like to run Chainfire's Recently (check the playstore) and I set it to max 6 apps with a limit of 6 hours. I only allow 2 Google search instances, no settings screens and I set it to remove each apps documents as well.
With the above, I experience very few slowdowns any more. I should add, that I am using MM roms.
Phone is the 6GB RAM 64 GB storage version.
For the last couple of weeks it slowed down to a crawl when it comes to launching apps. For instance it takes 18 seconds!, I timed it, to open Skype on my phone. Other apps also open very slowly. Once they are opened and kept in memory they are re-opened instantaneously so the problem is only when launching the apps the first time.
There is about 2.8GB RAM available, only 35% of storage space is used so there is no reason why the phone should run so slowly.
I have upgraded to Oxygen 5.0.4 but no change.
If I run it in safe mode I can't check if it's slow or not because no user apps are available.
I have cleared Cache and Dalvik cache repeatedly to no avail.
Any ideas would be appreciated.
Does this also happen on newly installed apps? It could have something to do with the ART optimisations on app launch but you experience it every time you open it from scratch?
1. your phone is fake or defective
2. you have installed some battery saver apps
3. you have flashed some custom kernels
I have used OP5T for over a month and I have to say, it's the fastest phone ever I have till now, before OP5T I got S7E, NoteFE, Mate 9 and IMO Mate 9 is really fast with Kirin 960 but OP5T is better and smoother than Mate 9 in many aspects. The things I missed so much from Mate9 are Sdcard and extremely long battery, the rest are fine for me on OP5T.
SOLVED.
It was an application called ProtectMyPrivacy, PMP for short. If I don't start it after rebooting for some strange reason it slows the phone down incredibly. It's a very useful application, it blocks all the sleazy apps form accessing, unbeknownst to the user, things like Phone Unique ID, Contacts reading, Calendar reading, Fine Grained Location, Mac address, etc. It's crazy how bundled apps we aren't even aware run in the background collecting all sorts of information and sending them to who knows where. Apps like AdMob, Flurry, AppBrain, AppsFlyer, InmobiFabric, Hockey App, etc. that are part of a regular app that we download but we have no idea they are bundled in. Sleazebags.
Anyway, PMP blocks all these bastards from spying on the phone but I need to start PMP manually every time I reboot the phone. I sent an message to the developer, SynergyLabs at Cornegie University, to let them know about the issue.