Hi all,
This is my first post here.
I have flashed the InsertCoin stable ROM 03/06 and I have to say it's great (despite the video playback bug). Recently I found another issue that bothers me a lot.
The problem I found is that the ROM seems to be killing non-active apps too aggressively. I learnt if I press "home" button in an active app, it should stay for a while until it is killed to free up memory. However, in my phone, the non-active apps are always killed within one minute even when the phone isn't running out of memory. Why it is an issue to me? Because:
1) It is killing the browser too fast. Usually I switched to other app, do some work, and back to the browser. Since the browser is killed it has to reload the whole page to restore the state. This wastes time and data.
2) Most importantly It is killing my music app!! I tried fire up HTC's music app, select a song, tap to play, leave the app and do other things like web surfing. The music app would surely be killed in a minute. This happens to other music playing app like Winamp.
This makes my phone a relatively single tasking one. I didn't install any 3rd party task killer because I never needed one. But I cannot find any settings regarding this "feature" on my phone.
I found people in this forum seeking help on how to kill some background apps. What I want is the opposite: How to prevent some background apps to be killed.
Anyone here has similar problem and has found a solution?
Thanks in advance!
on 1.0.8 i had no problems
on v45 (which is last 2D Rose version) you need to flash pre46test.zip in order to fix agressive app killing.
other than that i never heard of any complaints regarding apps being killed too quickly.
Thanks, dzumagos. Yes I am running 1.0.8 and unfortunately this happens on my phone
Maybe I'll try flashing the nightly version (v51) to see if things improve.
Whatever you do, don't use task managers and other memory scripts. Every developer makes his own memory parameters which suit his rom the best, so I think you are best off pointing baadnwz to this issue and see what he says.
erklat said:
Whatever you do, don't use task managers and other memory scripts. Every developer makes his own memory parameters which suit his rom the best, so I think you are best off pointing baadnwz to this issue and see what he says.
Click to expand...
Click to collapse
The ROM has HTC's ROM manager built in, and I didn't have any installed by myself. AFAIK the only difference between the Stable and Nightly version is the Rosie 3D homescreen that is missing in the Stable version, so I flashed 1.0.9 and unfortunately the problem persists.
And looks like I'm not eligible to ask on the development thread
Last year, when the "official" 2.3 Sense ROM came out, I waited until it was rootable and then installed it (yeah, love to be on the save side).
Among several issues there was a really annoying browser bug which FC at random times, especially when navigation quite fast between several pages (for example browsing forward and back on mobile optimized sites like the forum section of "heise-online.mobi"), I think it happens after pressing the back button.
I didn't like Sense, so I switched to Oxygen and later to CM7.
In CM7.1 I often had Browser issues again, but it did not FC but just stopped responding. Searching through the internet I found other ppl with the same issue... but no solution.
Now I'm using euroskank's CM7.2RC1 Build which is really great - but guess what: Browser crashes at random times when quickly navigation.
I checked the logs for stack traces and those crashes occur always in libwebcore.
So is there something broken in 2.3's webcore implementation?
I have used cm7.1 for quite a long time using ManU 2.0 SVS kernel. Try flashing that ROM and kernel combination, coz its the most stable combo i have found. No freezes, reboots or FCs. Press Thanks if my advice works
Can't say I noticed that on rooted stock roms, but haven't really used stock browser at all.
Sent from my HTC Desire using Tapatalk
I'm now on CM7.2RC1 which includes several webkit fixes, but browser is still crashing.
This often happens when quickly navigating between web pages (i.e. go quickly forward/backward in threads).
*sigh* maybe I'll try a full wipe and check if this still happens.... however wiping dalvik cache and clearing data of "Browser" and "HTML-Anzeige" (HTML-View?) should reset all to default - in theory...
erklat said:
Can't say I noticed that on rooted stock roms, but haven't really used stock browser at all.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Me too. Plus the fact that the internet cache is saved on the internal memory blows. Yeah I can link it to the sd-ext with a couple of commands but why bother when there are better 3rd party browser that does it for you and performs better.
Well, some 3rd party browsers like dolphin suffer from the same issue because they use the same webkit libs.
Had those hangs of CM7.1 in dolphin, too.
Also, I don't like firefox or opera, so there isn't much choice left...
I've been using Dolphin and I never encounter crashes with CM7 nightlies and this v7.2rc1. I'm using the mini version although I assume they use the same engine.
Maybe I should really do a clean wipe/reinstall.
I was carrying old data over from 7.1 (where I had hangs, not crashes, but some ppl reported them too in the cm forums - so I was not alone).
If it still happens, I'll create a bug report in the cm issue tracker.
I know how to collect logcat and stacktraces (tombstones), maybe this helps identifying this problem.
Edit: Done. Also happens with a clean full wipe installation - opened CM issue 4867
I have been experiencing some slow down and launcher refresh (when I come back from apps like flipboard, xda , g+etc) for last few days.
I don't think I had this issue with 4.1.1. To eliminate some possibilities I switched to stock launcher (from Holo launcher HD) and stopped using live wall paper but I still see this issue (launcher refreshes when I close some apps so probably launcher was earlier purged from the memory).
I used to face this issue on galaxyS with CM9 & CM10 but it was tolerable for galaxy S as it had less RAM (512 MB) but I don't expect this issue with gnex which has 1 GB ram.
I am using rooted stock 4.1.2 (I upgraded by flashing system and boot image on top of 4.1.1) with only one developer option on (usb debugging).
I haven't really started using any new app in this period (but I did upgrade my existing apps to the newer version). Most of the time my background running services are google location services,media, good application, betterbatterystats, notification toggle, battery widget and exDialer. I always keep google apps sync on. So my usage hasn't really changed between 4.1.1 and 4.1.2.
Could this be an issue with RAM management in 4.1.2 ?
Am I the only one facing this issue ?
If its just me then it must be some app that's causing this issue ?
Any help in narrowing down this ?
Sent from my Galaxy Nexus using xda app-developers app
ive never had browser reload on my gnex. maybe you have a bad app(s) using too much ram?
I have uploaded two logs (at https://www.box.com/s/j7nxvt2s4am6hbd82ppq ) of 2 instacnes where my launcher refreshed as it was purged from memory (look for holo launcher in the log). I have faced this issue with stock launcher too but probably with less frequency.
Please let me know if someone can advise based on the uploaded catlogs.
Hi,
First of all, I appreciate that you're taking some time to read my topic
I've got a problem with my One V for a long time now. Overall, the performance of my phone is great. But when using certain apps, for example, a browser (doesn't matter which one, I tried stock browser, Chrome, Opera, Firefox, Dolphin, enz) my phone gets laggy and then completely locks up until I can't even get the screen back on and I have to hard reset it. The problem is most pronounced with browsers but I know that apps like Facebook can trigger the problem too.
I already addressed this problem earlier in the threads of ROMs I was using, but because I think most of you don't have a good idea of what I mean so I made a video to demonstrate the problem.
I have this problem with most custom ROM's. Lloir's and Maxwen's CM10 had this problem and Shpongle (which I'm currently using) has it. I used AOKP for some time back and I'm pretty sure that AOKP didn't have the problem, but unfortunately that ROM had other problems (sound not working, and that's a pretty big deal you know)
I never used stock ROM so I don't know if it's present there as well.
I feel like I'm the only victim of this issue and I've tried everything to get it solved. It's just very annoying because can't use my phone without having to reset it 1-3x per day. I'm at the point that I have no idea what could be causing it and I don't know how to solve it.
I already tried using Turbo Boost, but that didn't solve it. It is very probably not a memory issue; my RAM is not full when the problem shows up.
I'm thinking about trying to revert to stock... Maybe the issue is not present in stock ROM. But I hope you guys can help me in some way... Maybe there are other users with the same problem?
Try downloading greenify. I have this problem, and just set Facebook and other draining apps to hibernate when my screen shuts off....problem solved.
Sent from my One V using xda app-developers app
Compizfox said:
Hi,
First of all, I appreciate that you're taking some time to read my topic
I've got a problem with my One V for a long time now. Overall, the performance of my phone is great. But when using certain apps, for example, a browser (doesn't matter which one, I tried stock browser, Chrome, Opera, Firefox, Dolphin, enz) my phone gets laggy and then completely locks up until I can't even get the screen back on and I have to hard reset it. The problem is most pronounced with browsers but I know that apps like Facebook can trigger the problem too.
I already addressed this problem earlier in the threads of ROMs I was using, but because I think most of you don't have a good idea of what I mean so I made a video to demonstrate the problem.
I have this problem with most custom ROM's. Lloir's and Maxwen's CM10 had this problem and Shpongle (which I'm currently using) has it. I used AOKP for some time back and I'm pretty sure that AOKP didn't have the problem, but unfortunately that ROM had other problems (sound not working, and that's a pretty big deal you know)
I never used stock ROM so I don't know if it's present there as well.
I feel like I'm the only victim of this issue and I've tried everything to get it solved. It's just very annoying because can't use my phone without having to reset it 1-3x per day. I'm at the point that I have no idea what could be causing it and I don't know how to solve it.
I already tried using Turbo Boost, but that didn't solve it. It is very probably not a memory issue; my RAM is not full when the problem shows up.
I'm thinking about trying to revert to stock... Maybe the issue is not present in stock ROM. But I hope you guys can help me in some way... Maybe there are other users with the same problem?
Click to expand...
Click to collapse
Very strange... maybe your phone's motherboard is broken, so when WiFi transmitter gains signal and send it forward, there's some point in that way that causing problems... I'm talking about WiFi cause you haven't said what are you using: 3G/4G or WiFi... or maybe your router is causing those problems...
And you haven't got back to stock completely... I propose U to flash myONEv 9.5 or Ignorance v3 (best performance and the smoothest I think) and check if that problem repeats... addintionally you can compare CM10/AOKP with custom-Sense ROMs for me custom-Sense ROMs are better than CM10/AOKP
sellersj27 said:
Try downloading greenify. I have this problem, and just set Facebook and other draining apps to hibernate when my screen shuts off....problem solved.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
It's not like it is "draining apps". The problem only appears when the screen is on and I use the apps actively. If the phone is so slow that I can't get the screen back on, most of the time it 'recovers' again when I wait for 30-60 minutes with screen off. Off course I don't have the time for that so I hard-reset it.
So I don't think Greenify will do anything in my case.
parkourz said:
Very strange... maybe your phone's motherboard is broken, so when WiFi transmitter gains signal and send it forward, there's some point in that way that causing problems... I'm talking about WiFi cause you haven't said what are you using: 3G/4G or WiFi... or maybe your router is causing those problems...
Click to expand...
Click to collapse
It doesn't matter whether I'm using WiFi, 2G (GPRS/EDGE), 3G (UMTS) or HSDPA.
Second, it doesn't look like the problem happens with internet access in general. It more happens with certain apps. For example, I can stream video's from Dropbox perfectly. In that case I both have heavy CPU/GPU usage (because of the video decoding/playback) and heavy internet traffic (because I stream from Dropbox), but I have no problems.
And you haven't got back to stock completely... I propose U to flash myONEv 9.5 or Ignorance v3 (best performance and the smoothest I think) and check if that problem repeats... addintionally you can compare CM10/AOKP with custom-Sense ROMs for me custom-Sense ROMs are better than CM10/AOKP
Click to expand...
Click to collapse
Yeah, I think I'm gonna try that. Thanks for your help!
Today I installed myONEv RC9.5 FX+ and it is quite a bit smoother, but that goes for every fresh ROM install
I have to test for a few more days to give an answer about whether the problem is fixed or not. The problem seems to be a lot less pronounced with fresh ROM installs and I need to use it some time to be sure.
However, so far I don't think I really like Sense ROMs I've come across several things that I like better in Shpongle or CM10. For example, in most of those ROMs you get in settings an extra options menu with performance settings (overclocking, kernel settings, I/O scheduler, compcache), auto-brightness levels tweaks, auto-rotate tweaks, softkeys settings, statusbar tweaks and such. Does anyone know good compact app that features all this?
Oh, and it's only Android ICS 4.0.1 I was used to JB 4.2.2
Compizfox said:
Today I installed myONEv RC9.5 FX+ and it is quite a bit smoother, but that goes for every fresh ROM install
I have to test for a few more days to give an answer about whether the problem is fixed or not. The problem seems to be a lot less pronounced with fresh ROM installs and I need to use it some time to be sure.
However, so far I don't think I really like Sense ROMs I've come across several things that I like better in Shpongle or CM10. For example, in most of those ROMs you get in settings an extra options menu with performance settings (overclocking, kernel settings, I/O scheduler, compcache), auto-brightness levels tweaks, auto-rotate tweaks, softkeys settings, statusbar tweaks and such. Does anyone know good compact app that features all this?
Oh, and it's only Android ICS 4.0.1 I was used to JB 4.2.2
Click to expand...
Click to collapse
All those things: NO... For OC and schedulers U can use NoFrills CPU Control or SetCPU or anything you will find... for statusbar tweaks, Ignorance ROM have additional flashable zip that offers centered clock + normal/% battery and right-side clock + normal/% battery... for RAM tweaks, you can flash ksm.zip from myONEv 9.5 thread or Triple Swap from here... as I remember Nova Launcher have softkeys settings
Compizfox said:
Oh, and it's only Android ICS 4.0.1 I was used to JB 4.2.2
Click to expand...
Click to collapse
It's 4.0.4 actually.
Have you tried Xtreme Turbo Booster (I think that's the name)?
MameTozhio said:
It's 4.0.4 actually.
Have you tried Xtreme Turbo Booster (I think that's the name)?
Click to expand...
Click to collapse
xtreme turbo bosster ?
The browser lag is not just you. I have tried every single browser offered on google play and they all become slow and unresponsive. The only browser I use is stock 4.1.2 browser. Anything else is garbage. Including Opera Mini (not because of lag but because of its bugs in reloading pages when submitting passwords,text in boxes in general..over all its a piece of sh*t) and so are the other "mini" styled browsers. Seems the browser developers have forgotten that they are developing browsers for PHONES..NOT COMPUTERS!! Hell many of the browsers bloat up after install to sizes larger than many desktop browsers..what a joke. I down rate them all on the market.
Curtis1973 said:
The browser lag is not just you. I have tried every single browser offered on google play and they all become slow and unresponsive. The only browser I use is stock 4.1.2 browser. Anything else is garbage. Including Opera Mini (not because of lag but because of its bugs in reloading pages when submitting passwords,text in boxes in general..over all its a piece of sh*t) and so are the other "mini" styled browsers. Seems the browser developers have forgotten that they are developing browsers for PHONES..NOT COMPUTERS!! Hell many of the browsers bloat up after install to sizes larger than many desktop browsers..what a joke. I down rate them all on the market.
Click to expand...
Click to collapse
That reminds be a lot of chrome. It's only smooth on my Nexus 4.. on my one v it's super slow.
MameTozhio said:
That reminds be a lot of chrome. It's only smooth on my Nexus 4.. on my one v it's super slow.
Click to expand...
Click to collapse
you will find that true for firefox,next,one,dolphin,opera and all the others available. developer disregard for device limitations and posting that their work is "compatible" with "any" device of certain android types. when they are truly designing for only high end devices. a bunxh of jokesters.
Curtis1973 said:
you will find that true for firefox,next,one,dolphin,opera and all the others available. developer disregard for device limitations and posting that their work is "compatible" with "any" device of certain android types. when they are truly designing for only high end devices. a bunxh of jokesters.
Click to expand...
Click to collapse
The fastest and cheapest (low mobile data usage ) browser is Opera Mini... and I haven't seen any bugs in it :good:
i beg to differ. opera mini has several bugs that go back as far as opera mini 4. inputting text in text fields like password,username and general reply/post boxes results in a page reload that requires user to start all over again...and sometimes this reload loops infinitely. the bug starts with operas flawed data compression system in which they crunch and preload pages on their servers before ypu actually get the content. its because the compression via srrver versus direct to device mucks up the transmission of the types of data mentioned. and i wont even start on the "new" opera mobile...what a joke that has become. no opera mini is not bug free by any means. and even after many users submit bug reports about the reload/lost data bug...opera does nothing...either because they cant fix it or dont think its there. well it is and has been for years..
Curtis1973 said:
i beg to differ. opera mini has several bugs that go back as far as opera mini 4. inputting text in text fields like password,username and general reply/post boxes results in a page reload that requires user to start all over again...and sometimes this reload loops infinitely. the bug starts with operas flawed data compression system in which they crunch and preload pages on their servers before ypu actually get the content. its because the compression via srrver versus direct to device mucks up the transmission of the types of data mentioned. and i wont even start on the "new" opera mobile...what a joke that has become. no opera mini is not bug free by any means. and even after many users submit bug reports about the reload/lost data bug...opera does nothing...either because they cant fix it or dont think its there. well it is and has been for years..
Click to expand...
Click to collapse
Opera Mobile Classic is the only decent browser IMO, it's the only one that loads pages faster than any other browser for me.And the UI isn't that ****ty new one, it's the one from the old symbian days, the look that actually worked.
Steam. said:
Opera Mobile Classic is the only decent browser IMO, it's the only one that loads pages faster than any other browser for me.
Click to expand...
Click to collapse
the stock browser is spot on versus opera mobile classic,but its a very close second. to bad opera went off on the deep end with that new crap they have up on the play store. even the apps icon sucks.
I have the same problem
But Opera mini next is so good to me.
Ultra FAST and stable
Opera mini next 7.5... Not old Opera mini
But the problem is not memory, it's because message cpu usage of these browsers
For Example Google Chrome run on 100% of cpu and Opera mini runs on 50% average with 10 open tabs!
Sent from my HTC One V using Tapatalk 4
rostamiani said:
I have the same problem
But Opera mini next is so good to me.
Ultra FAST and stable
Opera mini next 7.5... Not old Opera mini
But the problem is not memory, it's because message cpu usage of these browsers
For Example Google Chrome run on 100% of cpu and Opera mini runs on 50% average with 10 open tabs!
Sent from my HTC One V using Tapatalk 4
Click to expand...
Click to collapse
There's no Opera Mini Next in Play Store
parkourz said:
There's no Opera Mini Next in Play Store
Click to expand...
Click to collapse
Here it is :
https://play.google.com/store/apps/details?id=com.opera.mini.next.android&hl=en
rostamiani said:
Here it is :
https://play.google.com/store/apps/details?id=com.opera.mini.next.android&hl=en
Click to expand...
Click to collapse
I don't understand, I was seraching it for 20min with no results
Opera was good only in Symbian. In Android it's buggy. One browser is good.
Sent from my One V using xda app-developers app
My lollipop experience is this: battery life seems OK but less than I was getting with the elementalx kernel, the sound stutters especially when the screen is locked. Its pretty random but the buffer is underrunning at times. Which leads me to what's bugging me the most. With KitKat and the same apps installed I was getting roughly 800mb-1gb free of memory. With lollipop it starts out OK at boot but quickly starts eating up ram like candy. I've had Pandora force close in the background which is probably why I'm getting sound stutters because something is using memory and force closing services in the background. I'm using apex launcher and that constantly has to reload to. Before it very rarely reloaded. Also various widgets are having their services killed and I have to go and manually restart them. I've gone from 1gb free typically to like 3-400 mb free. Does L really use that much more ram? Also what about the damned "focus" on battery life they claimed? Its definitely worse here. Looks like this update was half baked if you ask me. I'm at least not getting horrible fps in games like some are claiming. And yeah the YouTube bug is really random and annoying. Anyone else have low memory issues??
Sent from my Nexus 7 using XDA Free mobile app
Same issue. But found the soultion
Facing the same issue. But what i came across is that maximum people who updated to lollipop via OTA are facing these.
Others who have side loaded it or flashed the new lollipop image are all fine. There are bugs in lollipop but atleast they are not facing the terrible issues like us. That battery life is insane , i cant use it as my daily driver with such pathetic battery life. But people who have updated it other than OTA are infact getting better battery than KitKat what Google claimed it to be.
Also the memory issue. Yes this is the main problem what we all OTA updaters are facing. This is called memory leak. I founded it over here. Few developers have explained it in detail - You should have a look.
They have suggested for a clean install of lollipop by complete flash or a factory reset. I have not done it yet. Too lazy to get the backup and all.
But have to try it as we are left with no other option. Check out this link for memory leak - tinyurl.com/pmjlol2
If you decide to install it yourself, use one of the current builds instead of the factory image. Google has pushed a few revisions out.