A temporary Xposed fix for part of Lollipop 5.0.x memory leak issues has just been released by tonyp.
It might be interesting for those of you running Lollipop ROMs and being annoyed by this issue.
According to tonyp, the Android 5.1 fix has already been implemented in CM12 for two weeks, so for those running CM12 nightlies there is no need to use this fix. The fix should therefore also be present in new versions of Lollipop CM12-based ROMs, but until then it could be a relief.
So feel free to test it and tell us if it shows improvements!
Related
Just released for the Nexus devices, so expect some of the (still) supported AOSP roms to roll this out by end-of-month - if not sooner. Please don't use this as an excuse to spam threads asking for ETA's, as all 4.4.3 discussion can go here until those respective threads go live.
Thank you.
CM11 4.4.3 is now available for s2 i9100.
CM11 4.4.3 is now available for s2 i9100.
any stable 4.4.3 version released? i flashed 4.4.3 slimsaber before and the random restarts kinda turn me off. I'm back to 4.3.1 and it's rock stable
jammerlee711 said:
any stable 4.4.3 version released? i flashed 4.4.3 slimsaber before and the random restarts kinda turn me off. I'm back to 4.3.1 and it's rock stable
Click to expand...
Click to collapse
Did you do a full device reset? I usually dirty flash until 4.4.2 latest release, then fully wiped clean my device before jumping on 4.4.3.
4.4.3 Really looks great
MrRaines said:
4.4.3 Really looks great
Click to expand...
Click to collapse
I'm thinking about install CM11 M7 on my s2, what do you guys think about it? Bugs and something like that?
CM11 M7 works flawlessly... but:
- there is no default ringtone so if u wiped your /data you will hear silence when someone calls u
- there is no kernel with working usb-otg nor usb-hdmi around for this release, but DorimanX team is looking on to that.
- CM's gapps not working (not ready for 4.4.3 obviously), use pa_gapps (http://forum.xda-developers.com/showthread.php?t=2397942) - in my case only micro was small enough to fit with that new huge CM
- that kitkat /storage/sdcard0 read-only issue makes lot of apps to just crash !!
Besides above it works pretty well. Wifi stable, hsdpa stable, calls/sms fine, browser fine. Can't find anything more not WAI.
At this time I'd suggest NOT flashing DorimanX on newest CM 11 M7.
If u wiped /data partition you have to recreate some default structures (eg. DCIM or camera and gallery won't work).
GPS was fixed a few nights ago
Most external SD card bugs are fixed excluding new internal format feature (let me know of this changes I stopped trying it since it was so buggy and more importantly I didn't like it. (Apps need root or 6.0 updated permission requests to write to external)
Battery life is great
Xposed is working with most modules
Network performance is great
Benchmarks run stable and good scores
Bluetooth issues fixed maybe not all but most I haven't has any issues
Toy box updated in recent nightly
I HAVE RAN CM13 SINCE FIRST NIGHTLIES AND I THINK IT'S FINALLY WORTHY AS A DAILY DRIVER FOR MOST CM LOVERS THAT DON'T NEED A PERFECT RELEASE
The only S5 Kitkat ROMs I've found either haven't been updated in over a year, or many users are reporting severe bugs like no camera support, or severe battery drain issues.
I'm just trying to get an app called Winulator running so I can play Starcraft: Broodwar on android, but it isn't working and one user said that is because Lolipop broke it (I'm on 5.1.1 atm). The app is no longer supported so I don't think it will ever run properly on 5.x. If anyone knows of a way to emulate 4.x for just 1 app maybe that would be the best shortcut for me overall here.
Barring that, could someone please recommend a guide to installing a lightweight, power-user-oriented ROM that is 4.x or older and has excellent battery life? I was going to try the official 4.4.4 VanirAOSP release but there are too many reports of poor battery performance in the last 2 pages of that thread for my liking.
I think the first thing I need to do is unlock the bootloader, and I've yet to find a definite answer on the best method of doing this from FOL1 (12/15). It seems I will need Odin on my PC and I have it. I've also started backing up all the data from my phone by manually copying/pasting to my PC.
I guess once everything is finally backed up (it's taking FOREVER, explorer literally been calculating time to copy for 10 minutes now just on the phone/android folder), then I will try and flash the official 4.4.2 VanirAOSP ROM since that one doesn't have any reports of battery issues and possibly only the camera and a few things won't work.
BTW, is there a step specially to unlock the FOL1 bootloader that I am missing, or can I just flash that ROM with Odin straight up? I found a comment stating NOT to flash 5.1.1 with Odin or I'd be stuck on Lollipop until some new bootloader-unlock method comes out. The 5.1.1 I'm running wasn't flashed with odin it was sent OTA and I've never rooted or had custom rom/bootloader, so I should be good on that I guess?
I am actually about to dive into this, if no one has any suggestions for me: http://forum.xda-developers.com/showthread.php?t=2752995
So I'll just pick one at random then? Thanks for the help...
You haven't even listed your model S5 or the ROM it's running now
And of course KK hasn't been updated in over a year, Lollipop and Marshmallow are released, they're not going to keep updating KK when a newer version of Android is released
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
I recently bought a used Lenovo A6000+. Using it for the first few hours did not reveal any major flaws. However, shortly afterwards I realized that the Phone used to switch off by itself when left unattended.
After verifying that my assumption is true, I proceeded to flashing the stock Lollipop ROM. I did so because I thought the problem was due to a flaw in the firmware. Plus, the 'About Phone' section in the Settings app showed clearly that my phone is a Lenovo A6000, with 8GB internal storage and 1GB RAM, while CPU-Z said that there is 16GB internal and 2GB of RAM, which tells that it is an A6000+.
The Lollipop ROM is worse than what I had anticipated. It lags like hell on the device, and is filled top to bottom with bloatware. Plus, the problem didn't get rectified even a bit. Worst, it started switching off even more regularly, and it wouldn't start unless I took out the battery and put it back in again.
If someone has devised a way of getting past this problem, be kind enough to mention it below.
@techfreak13, I don't know what's causing this issue but I can tell you that the stock Lollipop was a nightmare. Either you stay with stock KitKat or you can flash any of the other various ROMs available for this device. But, do note, that if you want to move from Lollipop (or Marshmallow or Nougat) based to KitKat based ROMs or vice versa, you'll first need to flash the stock ROM only. Then only you can flash the custom ROMs. Also different versions of TWRP are needed to work with the Kitakt and the other Lollipop/+ ROMs. TWRP 2.8.6 no image is for Kitkat while the latest verion 3.1.0 can be used for Lollipop+ Android versions. Since there is no unified thread for all the mods and roms. You'll have to dig deep into the forums to get the links. Good Luck to you. I hope you'll be able to solve the problem.