So I'm noticing I get home redraws after a day or two of use without restarting. When I freshly boot my phone, I have about 1 gb of free RAM and after a day or so, it'll drop to around 600 mb. I'm rooted and installed the memory leak fix for xposed but it doesn't seem to be working. Any suggestions?
Thanks.
txv0 said:
So I'm noticing I get home redraws after a day or two of use without restarting. When I freshly boot my phone, I have about 1 gb of free RAM and after a day or so, it'll drop to around 600 mb. I'm rooted and installed the memory leak fix for xposed but it doesn't seem to be working. Any suggestions?
Thanks.
Click to expand...
Click to collapse
The memory leak fix is only for when you turn off the screen. There are a bunch of other memory leaks in android 5.0.x and even 5.1. The only way to get rid of them is to update to android 5.1.1 (and later?).
Different rom (debloated) , custom kernel, disabling unnecessary Google play services via MyAndroidTools. All can help. As I heard, screen off memory leak is not an issue with g2 lp, but there are some other leaks, yes.
The best ram management I had was with dorimanx kernel (currently using it, 2.9 for vs980) on stock lp rom (xdabbeb's 3.1.0). It has some tweaks that help fix some of the memory leaks found in 5.0.2. If you are on STOCK g2 rom (not ported) I suggest you to try it for yourself. It seems to me like it makes a difference and it can be set as an scheduled event so you don't have to clean ram, cache and whatnot manually. Check the screenshot for the options via dorimanx stweaks app that comes with the kernel
Related
OK, as you know an official 4.3 is out and after Wanam got a NON-WIPE version based on it the temptation was too big.
I was running for a very long time a dual-boot system based initially on Siyah kernel and lately on Googy-Max kernel, and the main ROM was a Sammy 4.1.2 (which also happens to be quite customized, with a lot of bloatware removed and the rest frozen in Titanium or Greenified; also using Apex as launcher and DialerEx as dialer).
FIRST STEP - make a good EFS backups (as in save it in more than in one place) - I was running with an older EMF1 modem (which I found to be VERY power-efficient for my needs) using the old EFS format, (for the moment) it is said that 4.3 Sammy ROMs will need the newer EFS format and will upgrade you (probably by installing the new modem). Also in this step it is a good idea to backup your ROM(s) from recovery (and direct that to the external SD). It is also a good idea to have around "just in case" the kernel(s) and whatever else you think you might need to restore things in case something goes wrong. Also having a Titanium Backup of your LATEST stuff on the external SD is a very good idea.
2nd STEP - get a NON-WIPE ROM based on the Sammy 4.3 - I used GT-I9300_WanamLite.XXUGMJ9.V7.2.NO-WIPE.zip
3rd STEP (optional stuff) - in case you want to keep your old Sammy configuration and/or dual-boot - copy (in the special dual-boot recovery) your Sammy main ROM on both slots - I normally have my main 4.1.2 as the 2nd ROM (which is set as default = primary), and I do all the tests on the 1st ROM (mostly since some aroma installers work best on 1st ROM). So I kept my main 4.1.2 as the 2nd ROM and I made a copy of it to 1st ROM.
4th STEP - install the NON-WIPE 4.3 (in my case from Philz Recovery over the 1st ROM as an upgrade). It worked pretty well but it took a rather long time (10+ minutes). At the end I encountered 2 minor problems - during the upgrade of the Sammy Calendar items it kind of remained forever there (with the circle rotating but after 10 more minutes I decided it was a little too much and I forced a power off by keeping the power button pressed 7-9 seconds; after restart it went over OK; at a later time I got a message that media scanner crashed but after updates it seems OK).
5th STEP - update everything in the new ROM and configure it to your taste. IMHO you MUST try Xposed + Wanam Xposed - that one is great.
After a large number of updates, restarts, Wanam-related configurations + obligatory restarts and Greenify-related stuff I got EVERYTHING to work PERFECTLY in the new 4.3, so a few impressions on that:
- things are definitely a little snappier in 4.3
- the new settings are kind of different but not that much
- for me it was a major point that EVERYTHING was kept/upgraded - all my contacts were still there (with the custom pictures), Sammy calendar items and so on; the one thing that I had to restore manually were the custom ringtones;
- this version does not repartition and does not change your bootloader/recovery, but the Sammy official one is said to do that and to replace your bootloader; the free space is kind of low in /system without the repartition but IMHO is still perfectly usable;
- battery life over night looks OK for a Sammy kernel but is a far cry from what I was getting with custom kernels in 4.1.2 - about 8% discharge over night vs. only about 2%
- the best two new features for me - the torchlight in lockscreen (with volume up 2 seconds) and the 3-tap-zoom (standard Android stuff since 4.2.x)
- there is a very tiny delay when unlocking - some people claimed it was like 2 seconds but they are delusional, it is well under 0.5 seconds and I am not bothered by that AT ALL; EDIT: OK, I have now seen a few times something clearly longer than one second, it seems to be a little variable, I have yet to determine on what
- what bothers me a little is the PIN-unlock dialpad - I have seen the same in CM/AOSP before and it is kind of ultra-laggy (and pretty small) compared to the 4.1.2 Sammy PIN-unlock dialpad; on the other hand the 4.3 Sammy keyboard feels a lot better/faster than the ported Note2 keyboard that I am using in 4.1.2 :good:
- camera also works OK, the new Sammy media player is also OK (but voice commands are tricky on it); for the moment the lockscreen for me is "stuck" in the 'safe mode" enforced by Sammsung by some setting of policy; for me is not a problem but I would like to know more about this.
KIND OF DUAL-BOOTING
Googy-Max is not yet fully dual-booting the new Sammy 4.3 (but IMHO is VERY close - 4.3 boots and seems to be seen over USB, only the video driver is not correctly initialized), but there still is a way to get a kind of dual-booting - it is no longer a 2-click 10-seconds thing but instead a 10-click 50-seconds thing but still works - I have Googy-Max-Kernel_1.7.8_CWM.zip and Archi_Flasher_Repacked_Wanam_Stock_XXUGMJ9_Kernel.zip in the root of the internal SD and I only need to restart to recovery and write the 6-8 MB of kernel; when the Sammy stock 4.3 is written it automatically starts the 1st (standard) ROM = 4.3, when Googy-Max is written it was set as default for the 2nd ROM so it goes automatically to my old 4.1.2
REMEMBER - everything on internal SD is the new "4.2.x and newer" style - in 4.3 it goes to /data/media/0 and in 4.1.2 it goes to /data/media. Eventually specific configuration for that must be done in Philz Recovery and Titanium Backup.
I am still doing some battery tests over the next days - this night I want to test if the new BUUGMJ3 modem is part of the power-consumption differences so I will test it in the old 4.1.2 and with Googy-Max. There are many other small things to test, I will eventually add those here once done.
EDIT: A BETTER KERNEL FIXES THE LAGS
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
http://yank555-lu.net/viewtopic.php?p=4594#p4594
Also it might not be impossible that a true dual-boot Googy Max might be ready after the weekend or so.
Quite confuse here
How you dual boot for stock 4.3 as primary Rom & stock 4.1.2 as secondary Rom?
I know latest googy kernel not supporting stock 4.3 yet
Sent from my GT-I9300 using XDA Premium 4 mobile app
MsElise said:
Quite confuse here
How you dual boot for stock 4.3 as primary Rom & stock 4.1.2 as secondary Rom?
I know latest googy kernel not supporting stock 4.3 yet
...
Click to expand...
Click to collapse
It is not the very easy "2-click 10-seconds" dual-boot with a special dual-boot kernel, it is the more complex "10-click 50-seconds" dual-boot where you have two kernels as zip that you can install from recovery (it still takes like 10 seconds to write the kernel but since you must boot in recovery you are going to lose closer to 50 seconds when you decide to switch) - the stock Sammy 4.3 kernel (pre-rooted and processed by Wanam and repackaged by Archi) will always boot to the 1st ROM, while the existing Googy-Max (1.7.8 as we speak) will go to whatever is set as default for it - and in my case I have Sammy 4.1.2 set as default in 2nd ROM slot.
A BETTER KERNEL FIXES THE LAGS
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
http://yank555-lu.net/viewtopic.php?p=4594#p4594
Remember that if you encounter root-related problems (or eventually you are left at the Samsung boot logo) you probably need to write this from your recovery:
http://download.chainfire.eu/345/
Also it might not be impossible that a true dual-boot Googy Max might be ready after the weekend or so.
xclub_101 said:
...
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
...
Click to expand...
Click to collapse
OK, I am now really impressed with the latest yank.lu kernel :good:
With the default (zzmove) governor and almost all default settings from the beta2+ aroma (except no quick charge and only 400 MB zram) I got about 1% over night, I am now keeping this configuration for extra testing for a few more days :good:
can run the stock rom 4.1.2 and **** rom with 4.3 ????? :fingers-crossed:
Since I updated to a 4.4.2 TouchWiz ROM, I've been getting memory leaks after a week and a half or so of uptime on my AT&T i337. I notice that apps need to be reloaded shortly after using them previously, and even Nova launcher is getting kicked out of memory. The only fix is a restart. Looking through running services and cached apps before clearing memory shows almost everything has been removed from memory to make room for whatever phantom process is taking up all the RAM. The screenshot attached was taken after using the option to clear RAM. Anyone have any ideas? Thanks!
Details on my setup:
SHOstock-i v5.0 (based on the NB8 firmware for the i9505)
Upgraded to MLD kernel in order to run 4.4.2 TW ROMs
Safestrap 3.71
Hi everyone,
Until recently I've been using a KitKat based ROM and I was pretty OK with how my NOTE 3 SM-9005 was performing. However, a few days ago I decided to try a Lollipop based ROM and the problems started. I had similar problems with 3 different ROMs with great reviews. My battery went, for example, from 100% to 15% in ONE HOUR while streaming from YouTube. It never did that before. Also, It sometimes gives a "system stopped responding" error or something like that (it's like the equivalent of explorer.exe crashing on Windows) and after a few seconds it starts working again. Other system apps crash as well every now and then and sometimes the phone just decides to restart by itself.
I initially used Philz recovery and after the initial errors I switched to TWRP and started from scratch. I completely wiped my system internal space before flashing and, of course, I wiped dalvik cache and cache before and after flashing the ROM. I only used recommended gapps. Also, I did not restore any system apps. I started from scratch after the installation and the problem is the same.
To be more exact, I tries flashing so far the following ROMS, experiencing more or less the same problems on each:
temasek's UNOFFICIAL CM12.1
AryaMod V5.4 TW Lollipop Official BOB6
BlissPop 3.5 Unofficial
I also tried the Dirty Unicorns v9.4 ROM from the Original Android Development section but this one went on a reboot loop initially after the first restart so it never really even installed.
At this point I believe I might have done something that I should't have, but it seems strange because this is not the first time I am flashing a new ROM and I never had problems in the past. Also, my NOTE 3 SM-9500 did not have any problem on my previous KitKat ROM. Did I miss something? Should I have used another kernel? If I understood correctly, the ROMs come with a recommended kernel already. If this is not the problem, what could it be? Should I have done any additional thing before flashing a Lolipop ROM after using a KitKat ROM?
I now installed an app for trying to find out what exactly drains my battery but this is not the only problem. The system itself is really unstable.
I would really appreciate some help, suggestions, or opinions. I really don't know what else should I be doing at this point.
Thanks a lot!
Apparently is the media server eating all that battery (currently 68%).
I will format the SD card hoping this fixes the issue.....but could this have something to do with the system error and, sometimes, restarts?
Well I really don't know what to say! A lot of people report battery problems on 5.0 just because they didn't wipe the phone while coming from KK! But you did, so that's no go. Battery life on LP is much better than KK for me, at least 20% better if not more. And I didn't face any system crashing issues either! Don't really know what's going on with you mate.
Someone suggested that maybe I shoud update the bootloader and modem to a Lollipop version but I really couldn't find any info on how to do that.
Formatting the SD card just slightly reduced the battery drain. The phone is still discharging like crazy. Any suggestion on how to update the bootloader and modem?
Thank you.
Hello.
At first, I am new in the forum, so hi to everybody and thanks for the job in this site.
I have a very big problem with Note 4 ( I can't use it right now). Since I rooted the phone and changed the rom (to Cyanogenmod 12) all apps stop constantly and in random way. I have tried everything (I think so), return to the stock rom (android 5.0.1), make wipes (cache, data...) and reinstall the rom from Samsung switch.
I don't know what to do.
More info: All apps stop but the gapps stop with more frequency. I sent the device to the technical service but they take it back because I have modified the software (knox 0x1).
Sorry for my english. I am from Spain.
Thanks.
Third party apps or system apps?
Did you install any battery saving or ram booster apps?
GrippingSphere said:
Third party apps or system apps?
Did you install any battery saving or ram booster apps?
Click to expand...
Click to collapse
All of them
No, I don't believe in those apps. The only thing that I did for imrpoving the performance was to intall CM12 (It works fine at first)
I thought that CM12 doesn't work well with the Fast Charging... Could it be?
Thanks.
It seems like you might've flashed a gApps package for an earlier version of Android than what Cm12 is (5.1.1).
Try a full device wipe, reflashing CM12 & a gapps for 5.1.1
Jishy420 said:
It seems like you might've flashed a gApps package for an earlier version of Android than what Cm12 is (5.1.1).
Try a full device wipe, reflashing CM12 & a gapps for 5.1.1
Click to expand...
Click to collapse
I tried that and It didn't solve the problem. I also reflashed the stock rom (with Odin). Without effect, the problem was not resolved...
Thanks for your help.
Hello
I’m using always latest ver. of Phantom kernel on Phronesis rom.
I have big problems with lags almost all time during use phone. I think that one of source this problem is low level of ram.
So I changed LMK to very aggressive mode. After this change is better but not perfect. On default LMK I have amazing lags. I couldn’t normally use phone. After change LMK to aggressive mode I have +/-320-350 free ram.
I tried do full wipe include Internal memory and flash clean rom. This help only on the beginning. After few days again it’s the same.
Phone’s lagging. During unlock phone, when I open browser, during opening Swiftkey, Message App, Phone App and other apps.
Interesting fact is that my wife on her Note 3 has similar problems. Our phones don’t work smooth like months ago.
I don’t know how to find source of my problems. I don’t have enough dev skills. Could You help me with advices what options in Kernel Adiutor change for example.
I tried change roms and kernels but this helped only for few days.
This happens on a stock rom too?
I preferred don’t flash stock rom again because of a lot of work with loosing root, root phone again, flash recovery etc.
I tried flash other custom roms and problem came back after few days.
I wonder if there is any way to identify the source of the problem.
up..... is there any solution yet ?