Has anyone else noticed that the flash is really slow on 4.4.2? I used flash alerts pro since 4.4 and on 4.4 I could set the flash to blink 6 times or more in under a second. Now on 4.4.2 its more like 2-3 times. I am currently running Liquid Smooth and its the same. I tested with the torch app and no change. Anyone know why?
Sent from my Nexus 5 using Tapatalk
Jacob030 said:
Has anyone else noticed that the flash is really slow on 4.4.2? I used flash alerts pro since 4.4 and on 4.4 I could set the flash to blink 6 times or more in under a second. Now on 4.4.2 its more like 2-3 times. I am currently running Liquid Smooth and its the same. I tested with the torch app and no change. Anyone know why?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Could be where the torch app was merged from. The torch app on Carbon ROM is very fast, no lag/stutter what so ever. On other ROMs however, I have noticed the latent period from the click activity and the actual flash coming on. If you check the repo where the torch was merged from, that's probably why. Many use CM yet lately, is had issues. See if any differences between the ROMs and that'll probably answer why so lagged flash.
RevelationOmega said:
Could be where the torch app was merged from. The torch app on Carbon ROM is very fast, no lag/stutter what so ever. On other ROMs however, I have noticed the latent period from the click activity and the actual flash coming on. If you check the repo where the torch was merged from, that's probably why. Many use CM yet lately, is had issues. See if any differences between the ROMs and that'll probably answer why so lagged flash.
Click to expand...
Click to collapse
See that's the thing. Its not just the torch app. Its every app that has a strobe setting. Its like the flash can't flash fast enough. Maybe something is different in the kernel that changed the flash rate. It worked fine on stock 4.4, but not on stock 4.4.2. Weird........
Sent from my Nexus 5 using Tapatalk
Jacob030 said:
See that's the thing. Its not just the torch app. Its every app that has a strobe setting. Its like the flash can't flash fast enough. Maybe something is different in the kernel that changed the flash rate. It worked fine on stock 4.4, but not on stock 4.4.2. Weird........
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The torch app is the cause, it's been reported a lot. With a faulty torch app, as I've read across many boards, the flash "happens to early in camera" or "not working" or "laggy". The flash rate, in your case, is probably due to this as well. With new merged torch from either CM or other sources lately, there has been A LOT of reports against it working/misfunction. What I can say is, try flash another ROM that works (could try Carbon ROM) and test the flash/strobing effects. If it works on that ROM, then it's the liquid smooth ROM/torch. If not, then it's the phone. But I looked into liquid smooth before but lately, they've had problems, one being the torch app.
RevelationOmega said:
The torch app is the cause, it's been reported a lot. With a faulty torch app, as I've read across many boards, the flash "happens to early in camera" or "not working" or "laggy". The flash rate, in your case, is probably due to this as well. With new merged torch from either CM or other sources lately, there has been A LOT of reports against it working/misfunction. What I can say is, try flash another ROM that works (could try Carbon ROM) and test the flash/strobing effects. If it works on that ROM, then it's the liquid smooth ROM/torch. If not, then it's the phone. But I looked into liquid smooth before but lately, they've had problems, one being the torch app.
Click to expand...
Click to collapse
Here's vids of what I mean.
Stock 4.4
http://youtu.be/IzVoLCKMInM
Stock 4.4.2
http://youtu.be/QvkN6x0Dto0
Jacob030 said:
Here's vids of what I mean.
Stock 4.4
http://youtu.be/IzVoLCKMInM
Stock 4.4.2
http://youtu.be/QvkN6x0Dto0
Click to expand...
Click to collapse
I see what you're saying, flash is slower. The reason, being on custom ROM and that the updates to Kitkat have been battery drain and camera issues are probably causing you the issue. The update to 4.4.2 probably caused the problem because of upgrades to camera/torch files. As before, if test another ROM quick and see if issue persist. If so, then it's 4.4.2 and, if not, then it was ROM related. Only reasons and change.
Related
Hey I just wanted to know peoples opinions on what is the best CM10 Rom so far. Especially considering the things that dont work like MMS or tethering or Netflix (I dont think any work with it though)
I like it. It's clean and boost free.
Sent from my SCH-I535 using xda premium
Just loaded everything looks good except camera or gallery doesn't work. Am I missing something?
AndroidGraphix said:
I like it. It's clean and boost free.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which CM10 rom are you running? Invis? The official CM?
llama555 said:
Which CM10 rom are you running? Invis? The official CM?
Click to expand...
Click to collapse
Official CM10 nightly
mms aint working yet but should in next official nightly. which should be in a few hours... other than that, official definitely had the most stable release!
NFC also isn't working but hopefully it gets fixed soon including MMS.
You'll probably just want to roll with the officials. Most everything you want has already been or is soon to be merged.
Anyone get WiFi tether to work? It worked for me on CM9
Just a question. Does CM10 have the long press volume feature to skip tracks while the phone is asleep? Love this about synergy
Sent from my SCH-I535 using xda app-developers app
What happened to the official thread in the original development sub forum? :what:
Sent from my SCH-I535 using xda premium
llama555 said:
Hey I just wanted to know peoples opinions on what is the best CM10 Rom so far. Especially considering the things that dont work like MMS or tethering or Netflix (I dont think any work with it though)
Click to expand...
Click to collapse
i have used about a day and here are my thought
unlocked bootloader
i have cleaned cache format factory reset before install
after boot i have loaded my app with data not bloatware with toolbox pro
using go launcher no live wall paper and juice defender
rest of app are... well just application and few games.
and here is real pro and cons
Pro
Fast, it does the job, google and now other jb features are works perfectly
unlock bootloader can be easily done thanks you adam.
boot time is faster than what i used to use AOKP milestone 6.1
Con
UNSTABLE, within half a day rebooted like 3~4 times while i was doing something
who know how many times it rebooted while i wasnt looking.. it seems more because from battery status
there are few blank spots. i have no idea what is wrong kernel perhaps?
i am not sure i thought CM is made from AOSP so i thought it should be pretty stable but i guess not.
also i have car blue tooth device with handset free (GROM) it wont connect and my logitech one works perfectly
DATA also not stable it think for battery it tries to turn it off (i think it's from juice defender) but takes about 10~15 seconds before i get the data
if you dont have problem with rebooting at random times, some glitches and no softkey (it's nightly so i cant really say it's bad rom)
this is the ROM.. it's faster than any rom i have tried.. what do you guys think??
maybe i should have tried longer but for me it was too unstable.
does cm10 have any critical bugs??
So, I was curious about a couple things.
First, how do nightlies work? Do you have to go and download a new file every single night and flash it? Or is there something working with the ROM that will flash a new version for you as it comes?
Second, I was curious as to when you guys think that CM10 for the SGSIII will be stable to the point where all major things, data, keys, gallery, camera, MMS, bluetooth, etc, are working reliably? I'm incredibly pleased with the stock experience, but there's always something to be gained from custom ROM's and I'm looking forward to being able to use CM10 I just don't want to miss a big part of my phone.
Not meaning to hijack the thread or anything! I'll throw in my two cents too by saying that I'd recommend the official CM10 based on the fact that MMS seemingly works currently and I'm unsure of how it's doing on the unofficial ROM.
syungyou said:
i have used about a day and here are my thought
unlocked bootloader
i have cleaned cache format factory reset before install
after boot i have loaded my app with data not bloatware with toolbox pro
using go launcher no live wall paper and juice defender
rest of app are... well just application and few games.
and here is real pro and cons
Pro
Fast, it does the job, google and now other jb features are works perfectly
unlock bootloader can be easily done thanks you adam.
boot time is faster than what i used to use AOKP milestone 6.1
Con
UNSTABLE, within half a day rebooted like 3~4 times while i was doing something
who know how many times it rebooted while i wasnt looking.. it seems more because from battery status
there are few blank spots. i have no idea what is wrong kernel perhaps?
i am not sure i thought CM is made from AOSP so i thought it should be pretty stable but i guess not.
also i have car blue tooth device with handset free (GROM) it wont connect and my logitech one works perfectly
DATA also not stable it think for battery it tries to turn it off (i think it's from juice defender) but takes about 10~15 seconds before i get the data
if you dont have problem with rebooting at random times, some glitches and no softkey (it's nightly so i cant really say it's bad rom)
this is the ROM.. it's faster than any rom i have tried.. what do you guys think??
maybe i should have tried longer but for me it was too unstable.
Click to expand...
Click to collapse
Ummmm.......I dont have any of those issues....I recommend full wipe and retry...with newest official from get.cm
Fallen224 said:
So, I was curious about a couple things.
First, how do nightlies work? Do you have to go and download a new file every single night and flash it? Or is there something working with the ROM that will flash a new version for you as it comes?
Second, I was curious as to when you guys think that CM10 for the SGSIII will be stable to the point where all major things, data, keys, gallery, camera, MMS, bluetooth, etc, are working reliably? I'm incredibly pleased with the stock experience, but there's always something to be gained from custom ROM's and I'm looking forward to being able to use CM10 I just don't want to miss a big part of my phone.
Not meaning to hijack the thread or anything! I'll throw in my two cents too by saying that I'd recommend the official CM10 based on the fact that MMS seemingly works currently and I'm unsure of how it's doing on the unofficial ROM.
Click to expand...
Click to collapse
Again, its fully stable. In your "second" part, literally every single thing you listed is fully working and stable. Except soft keys which were actually disabled because they have the same purpose as hard keys and just take up valuable real estate. Yes, nightlies are every night but you can dirty flash if you're lazy. You only really need to flash once a major fix or update has been merged. Just follow the changelogs.
And for you, based on what you reported as not-working, I'd also say you got a bad flash or something. Mine runs almost identical to what stock JB ran on my GNexus. Only better with mods
Sent from my Galaxy S3 using Tapatalk 2
I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.
Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app
Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.
had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.
I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive been using several 4.3 roms without one issue. Dirty Unicorn and Carbon have been prefect so far. Using latest twrp, full wipe and stock kernels.
Noremacam said:
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
Click to expand...
Click to collapse
What revision is your phone? Rev4? Rev5? My phone is a Rev0 and I'm not having any problems with running AOSP based ROMs.
I did too. I'm not sure WTF was going on, but ASOP/CM would be great for about a month, and then it'd start random rebooting. After it'd start random rebooting, the way to stop it would be to ODIN back to stock, and start over. Clean installs, nandroid restores, full formats.. None of it worked.
So here I stay on a crappy 4.1.2 TW ROM.. itching to return, but not really seeing enough improvements to warrant another go.
How are you restoring apps and data? I had problems after restoring via titanium backup, but when I restored selectively (just apps and data I really needed) with helium it's running fine.
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Noremacam said:
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Click to expand...
Click to collapse
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Check in terminal emulator.
Su (enter)
cat /proc/cpuinfo (enter)
This will give you the revision number and a lot more about your phone.
I have "rev 4" on my brown GS3 and have been running CM10.1.3. The only time my phone crashes/reboots is when I attempt to use the front facing camera with a third party camera app.
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Noremacam said:
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Click to expand...
Click to collapse
Download aLogCat from the play store and start the app. Then trigger the crash
Sent from my SCH-I535 using Tapatalk
What do you do if you can't cause it to crash? Mine are always totally random. It'll crash during a call, it'll crash while web browsing, it'll crash while locked in my pocket.. The only time it won't crash is when you want it to!
Do you just end up with a giant log file then or what?
I have to admit that I'm getting upset about my N5 several times a day now. Since I updated to Lollipop, I'm experiencing random issues with WiFi and 4G data connectivity, my LG G Watch is randomly disconnected sometimes and the worst thing presubably is the memory leak bug - when the phone is running for a few hours, I can't even browse the web with music playing in the background as the music is stopped when I open up more than one tab in Chrome. Obviously, I don't even think of navigating with Google Maps while playing music, and the Google Now launcher is redrawing every time I hit the home button.
I actually never had a custom ROM on my N5 as I was happy with the unmodified stock ROM, but now, I really need to get another ROM to be able to properly use the phone again.
After quickly browsing the forums, I think Cataclysm or something like CM12 or Paranoid Android is what I'm looking for. I figured out that the first one is based on 5.0.1 while the latter are based on 5.0.2... is there any noticable difference? And the most important question: Is the memory leak bug fixed in one of those?
Which ROM would you recommend if I just want to have a ROM that runs very well overall (I don't want to be required to flash every weekly build for bugfixes) and is updated fairly fast when new Android versions are released?
Either downgrade to KitKat (my recommendation) or wait for 5.1.
YassinTP said:
I have to admit that I'm getting upset about my N5 several times a day now. Since I updated to Lollipop, I'm experiencing random issues with WiFi and 4G data connectivity, my LG G Watch is randomly disconnected sometimes and the worst thing presubably is the memory leak bug - when the phone is running for a few hours, I can't even browse the web with music playing in the background as the music is stopped when I open up more than one tab in Chrome. Obviously, I don't even think of navigating with Google Maps while playing music, and the Google Now launcher is redrawing every time I hit the home button.
I actually never had a custom ROM on my N5 as I was happy with the unmodified stock ROM, but now, I really need to get another ROM to be able to properly use the phone again.
After quickly browsing the forums, I think Cataclysm or something like CM12 or Paranoid Android is what I'm looking for. I figured out that the first one is based on 5.0.1 while the latter are based on 5.0.2... is there any noticable difference? And the most important question: Is the memory leak bug fixed in one of those?
Which ROM would you recommend if I just want to have a ROM that runs very well overall (I don't want to be required to flash every weekly build for bugfixes) and is updated fairly fast when new Android versions are released?
Click to expand...
Click to collapse
There is no memory leak. Most reliable ROM is stock one. I would recommend 5.0.1, root, remove bloatware (yes, even Google can do that) and integrate all updates into system. Off course as @_MetalHead_ said, with 4.4.4 and Xposed you will also get a SuperRom.
_MetalHead_ said:
Either downgrade to KitKat (my recommendation) or wait for 5.1.
Click to expand...
Click to collapse
So the custom ROMs won't help with the issues I'm experiencing?
Downgrading to KitKat wouldn't be pretty as I'm using Lollipop's DNG capture feature with "L Camera" a lot...
zagorteney said:
There is no memory leak. Most reliable ROM is stock one.
Click to expand...
Click to collapse
But what is this about then? http://www.techtimes.com/articles/2...-android-5-0-1-lollipop-memory-leak-issue.htm
YassinTP said:
So the custom ROMs won't help with the issues I'm experiencing?
Downgrading to KitKat wouldn't be pretty as I'm using Lollipop's DNG capture feature with "L Camera" a lot...
But what is this about then? http://www.techtimes.com/articles/2...-android-5-0-1-lollipop-memory-leak-issue.htm
Click to expand...
Click to collapse
Custom ROM will only bring you more issues.
"The thread reveals that several Nexus devices ranging from the Nexus 7 (2013 model), the Nexus 4 and the Nexus 5 were affected by the bug." (from your article) - I own all of them and never ever experienced such a bugs on non of them.
There is a lot off diferent users with their own habits and (no)knowledge. Google must answer some way.
YassinTP said:
I have to admit that I'm getting upset about my N5 several times a day now. Since I updated to Lollipop, I'm experiencing random issues with WiFi and 4G data connectivity, my LG G Watch is randomly disconnected sometimes and the worst thing presubably is the memory leak bug - when the phone is running for a few hours, I can't even browse the web with music playing in the background as the music is stopped when I open up more than one tab in Chrome. Obviously, I don't even think of navigating with Google Maps while playing music, and the Google Now launcher is redrawing every time I hit the home button.
I actually never had a custom ROM on my N5 as I was happy with the unmodified stock ROM, but now, I really need to get another ROM to be able to properly use the phone again.
After quickly browsing the forums, I think Cataclysm or something like CM12 or Paranoid Android is what I'm looking for. I figured out that the first one is based on 5.0.1 while the latter are based on 5.0.2... is there any noticable difference? And the most important question: Is the memory leak bug fixed in one of those?
Which ROM would you recommend if I just want to have a ROM that runs very well overall (I don't want to be required to flash every weekly build for bugfixes) and is updated fairly fast when new Android versions are released?
Click to expand...
Click to collapse
Frank by Sykopompos .........For the N5
YassinTP said:
So the custom ROMs won't help with the issues I'm experiencing?
Downgrading to KitKat wouldn't be pretty as I'm using Lollipop's DNG capture feature with "L Camera" a lot...
But what is this about then? http://www.techtimes.com/articles/2...-android-5-0-1-lollipop-memory-leak-issue.htm
Click to expand...
Click to collapse
Honestly, I've had nothing but problems with Lollipop. I've tried stock, and a couple custom ROMs and there was no difference. I don't think it performs that much better than KK and I'm also not a fan of how it looks so I decided to keep all my devices on KK. Hopefully 5.1 will take care of all of the issues, I might upgrade then.
Or stay on LP and use this fix: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Primokorn said:
Or stay on LP and use this fix: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Click to expand...
Click to collapse
Doesn't have much effect, if any at all, people said they still have "memory leak issues".
If anything, there are probably multiple "memory leaks", and non-developers on XDA will spam links to "fixes" in every single thread/forum section, every time they're posted, and are under a placebo effect.
Then there are also the people who spam about Android 5.1 as if it's a huge improvement over 5.0–5.0.2.
The best band aid for this I've found is to use a kernel with zram compression like Faux kernel and the FauxClock app. I never though I'd have to resort to using compressed ram on my Nexus 5 but it was a godsend on reducing launcher redraws on an HTC Evo LTE running Sense with only 1GB of ram. The issue still pops up but much less frequently for me. BTW I have not run any comparison testing and this statement is pure anecdotal. I just have repeatedly observed on the same rom with the same exact setup for 2-3 months that using 3 kernels without zram required a reboot every day. On the same exact setup with zram I could go 3-4 days. A repeatable test for me was to browse on Chrome for a bit then go to the home screen. Without zram the launcher would redraw almost every time which was the same issue I had on Sense. With zram the launcher never redrew. Poo on Google for letting this issue go on this long without a fix.
I finally went back to lot kat for the same reason a month a go and couldn't be happier. The aggressive memory leak caused me to reboot several times a day. I liked cataclysm, but it's a modified stock nexus rom. So it contains all the same bugs the stock nexus rom does like the memory leak. It only adds new features.
Android lollipop memory leak not fixed in cm 12.1 with android 5.1.1 sources!!
I am using cm 12.1 latest nightlies which is based on android 5.1.1 sources and still I am faxing the lollipop memory leak issue and applications are restarting and the free Ram reduces up to 400 mb with no reason and the Apps will start restarting. I don't know when this memory leak will be fixed!
Hi everyone,
So i've tried 2 lolipop roms now (currently on the resurrection remix) and i'm experiencing very slow performance on all of them. Typical scenario i'm in an app (lets say chrome) i hit the center home button and then the app drawer button; its taking forever to show the apps and sometimes i will just get a black screen. Just earlier i went into settings and after clicking something it took a few seconds to actually register. I dont remember experiencing this slowness on kitkat or jellybean for that matter. Is it just me?
drkdeath5000 said:
Hi everyone,
So i've tried 2 lolipop roms now (currently on the resurrection remix) and i'm experiencing very slow performance on all of them. Typical scenario i'm in an app (lets say chrome) i hit the center home button and then the app drawer button; its taking forever to show the apps and sometimes i will just get a black screen. Just earlier i went into settings and after clicking something it took a few seconds to actually register. I dont remember experiencing this slowness on kitkat or jellybean for that matter. Is it just me?
Click to expand...
Click to collapse
No you are not.
I am experiencing the same and i am thinking everyone is experiencing this.
I would guess it's a Ram problem, cause thats the reason for all performance problems i had on this Phone, it has always been Ram/Ram-Management.
Take a look at the develpoment Page of CM12.
On the last Pages it seems like C has found a way to make this Rom really really Snappy, but he is still in testing.
Let's hope he will publish it soon.
Greetz Esok44
Check this rom, it's the fastest Lollipop rom I tried for now http://www.droidrzr.com/topic/61544-rom502aosp-aod-dark-updated-03-20-15
JoseBerga said:
Check this rom, it's the fastest Lollipop rom I tried for now http://www.droidrzr.com/topic/61544-rom502aosp-aod-dark-updated-03-20-15
Click to expand...
Click to collapse
its as good as the CM versions were a month or so ago. It seems the lollipop performance has dropped off lately as they've added in additional features. I'm on that rom right now because another one became unusable, but its got the same issues as other LP roms, namely multi-tasking and occasional awful performance (but yes, its probably the best of the bunch right now today as far as current roms go).
I'm seriously considering dropping back to KK
three west said:
its as good as the CM versions were a month or so ago. It seems the lollipop performance has dropped off lately as they've added in additional features. I'm on that rom right now because another one became unusable, but its got the same issues as other LP roms, namely multi-tasking and occasional awful performance (but yes, its probably the best of the bunch right now today as far as current roms go).
I'm seriously considering dropping back to KK
Click to expand...
Click to collapse
The memory leaks are to blame. Its not even device specific. They are trying to work on it. Word is CM12.1 should fix it, but i've heard mixed reviews on that. But yes, CM11 might be the best bet.
Sent from my ATRIX HD using XDA Free mobile app
5.1 fixes this
I just installed 5.1 by epinter and I have to say it runs amazingly fast, smooth and stable.
Everything that bugged me out is gone.
You can keep Whatsapp, Chrome and Maps in Memory - it's just awesome.
It's also very snappy and apps start a lot faster.
And keep in mind this is the first attempt at porting 5.1.
Did I mention the battery lasts almost 50% longer as well at my first day of usage?