Related
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
+1-I am having the exact same issues with same setup although I do have AutoKiller and it is set to Optimum.
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Jason kiDD said:
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Click to expand...
Click to collapse
Sorry, I should've mentioned that I DID try the BFS kernel (9/28 build) and it was after flashing kernels that I noticed it (mostly coincidence I'm sure) which is why I flashed straight CM6 to rule out the kernel
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Jason kiDD said:
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Click to expand...
Click to collapse
It happened with the stock .5 RUU ROM with the only modification being AndROOT...I RUU'd it back to .5 this morning and am going to ride it out untarnished to see if the problem replicates again. If so, I believe I will have successfully found it's a problem with the phone itself, and at that point take it to Sprint and see about paying the $35 for an exchange. I would do the OTA updates but if this shows its fixed I don't want to lose the ability to root, and I don't want to have to RUU back to .5 in order TO root. I was really hoping a dev who understands these ROM's better than I could chime in with some thoughts, but I guess I'll just have to keep test and tuning...I definitely appreciate these responses, though, and I'm happy I'm not the only one having this issue (though I'm still not happy it's happening lol)
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
t12icky0 said:
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
Click to expand...
Click to collapse
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Matt262 said:
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Click to expand...
Click to collapse
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
t12icky0 said:
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
Click to expand...
Click to collapse
Gotcha...if you check out my post count I'm a n00b to these boards, but I appreciate you not blasting me like I've seen others have that happen to them (for not searching ,etc)...maybe a mod could move this for me so I don't clutter the boards?
Dono74 said:
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
Click to expand...
Click to collapse
Exactly! Now if a resolution can be found...since I posted this in the wrong section, maybe there is a resolution and I just wasn't in the right spot to see it...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Decad3nce said:
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Click to expand...
Click to collapse
Actually when I flashed CM6 last night with no tweaks I didn't even install SetCPU or any kernels...just the one that came with it capped at 691.2...no battery tweak or anything
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Jason kiDD said:
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Click to expand...
Click to collapse
Still a mystery to me as to why it's happening with more ROM's than just CM6 though...oh well, I'll see how stock .5 unrooted treats me this weekend, and if I have the same problem happen again, I know it's phone related and not to be blamed on a ROM (which I'd like to make clear -- I do NOT blame CM6, Fresh, or NFXHero for my issues. I know the dev's spent a TON of time building everything for us to have something we would otherwise NOT have, and my sole reason for this post is really to find out exactly what is wrong with my phone, not necessarily with a ROM, and most importantly to find out if I'm the only one experiencing these issues)...I do appreciate all the help and responses, and I'm thoroughly impressed with XDA and the responsiveness of everyone
Just in case anyone was interested at all, my phone completely bricked today (stock .5 running all weekend no issues) and the culprit is the touchscreen and all buttons but power stopped working...sprint's overnighting me a replacement so evidently something got too hot at some point or the like...thanks to all for the responses, and to those who had similar issues (not related to the ROM you're running) then keep an eye out for imminent failure lol
I'm just curious because I get a lot of mixed answers, some users claimed they never had a problem and their sidekick 4G runs smoothly while others say their phone freezes and reboots way too often. Some have also said installing custom rom has fixed their phone.
I have my sidekick since last may it does not freeze nor reboot constantly the most that ever really happen was that the screen got mosit so it stop working. I have had no more then 10 battery pulls were the phone froze. Generally I pull the battery when I need to turn it off quick. (Used gingerclone,lighting rev2,glorious overdose,
Sent from my SGH-T839 using XDA
this question may perhaps be a bit tricky. some users, like myself, may have installed a custom rom, but that alone may not have fixed the lag. i installed b2tb, but still had a lag, and quadnrant score was the same before and after the flash. before b2tb, i was on stock firmware, and my quadrant score was in the 9s. after flashing, still in the 9s. screen lag was the same. a combination of voodoo lagfix and v6 supercharger have improved my quadrant scores to anywhere in the 11s or 12s. extremely little to no screen lag and no other noticeable performance lag at all. but simply flashing a custom rom did not fix my lag.
Try GenericGinger 2.0, I use it. I've never had my phone freeze, EVER. The speed is good, battery life great. Quadrant Standard score 1700+ google search it. I'm sure it won't be a waste of time
Sent from my SGH-T839 using XDA
I have been using this phone for a month, and it seems everything runs smoothly. just the battery life, like other smart phones, is disappointing.
Way too often for me, I'm not gonna lie and say it never did, evn though I love this phone to death. Too bad the only beastly phone out there with a keyboard close to the sk's is on verizon.
Then again, I'm not sure what I do that makes it freeze a lot.
Sent from my Sidekick 4G running PDT's Glorious Overdose.
Have had my phone reboot due to running completely out of memory some cases an others just wtf why you reboot momments. Worst issue i had was dealing with a possible issue in the built in kernal drivers for the bluetooth talking with my kia souls bluetooth stereo cause it seamed now an then at work (pizza delivery) the phone wouldn't disconnect correctly an would cause other issues, like...... overheating x.X an it wasn't the battery cause the face of the phone was hotter then the back where the battery was an by hot i mean like almost hot enough to cause a burn x.x! Love the sidekick an if the devs can make a rom that patches every single issue the factory firmware has in it I'll very likely go back to it, but at this time I'm happy with my edge speed on my captivate (daily driver) an X10 mini pro (amazing backup phone that never fails )
Completly forgot sbout this one weird issus. One day, I magically lost root, had bto reflash to get it back, I have no idea how it could've happened because I wasn't messing aroun with anything.
Ever happe3ned to any of you guys?
Sent from my Sidekick 4G running PDT's Glorious Overdose.
Uno if ur tired of rebooting getg a g2
Sent from my Htc Doubleshot running MIUI
I had some major issues yesterday with glorious overdose rom, I switched to gingerclone v2 and all is well now. Stock this phone is a turd....
I had to disable the trackpad today because in sunlight it would go hay wire and I wasn't able to browse online
is that what it is when i feel my screen going haywire? i'll be trying to text someone and then it keeps scrolling up the conversation and then trying to do a search throughout that convo...jeez i thought it was just a nasty bug haha i'll have to disable it then, i dont use it anyways...wish they would have brought back the trackball from the SKIII....now THAT trackball was cool.
I disabled it and now im not having issues with it. I get this annoying browser lag tho and I need to stop that. I am looking to get a different phone now. Im sure someone who is a heavy texter would love to have this phone...
oZerGx said:
Try GenericGinger 2.0, I use it. I've never had my phone freeze, EVER. The speed is good, battery life great. Quadrant Standard score 1700+ google search it. I'm sure it won't be a waste of time
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
Omg! This ROM is perfect! This is exactly what I've been looking for! I wish I could hit the thanks button a billion times!
4th Option
4th option - Factory Reset, Rooted, added App Killer and uninstalled most of the Bloatware (Like DriveSource)
works much better now, even with the Stock ROM.
---------- Post added at 10:35 AM ---------- Previous post was at 10:28 AM ----------
xtrem88 said:
...I have had no more then 10 battery pulls were the phone froze. Generally I pull the battery when I need to turn it off quick....
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
Push PowerButton and Volume button [+ or -] at the same time for 10 seconds. This is a little faster & easier than a battery pull.
For a while I was using Ice Cream Sandwich v2.0 Domination with the ICS launcher removed and ADW launcher in its place. Everything was fine except for the Gallery. It would take forever to load picture, and occasionally, it would reboot my device if it took too long. I just switched to GenericGinger 2.0, and I've had no problems with crashes or reboots.
I'm running Gingerclone w/ Voodoo Lag Fix and V6 Supercharger Aggressive 2. Using Tegrak to OC up to 1.152 and I'm consistently pulling quadrant scores of 2200+.
On the stock ROM the phone froze and rebooted frequently. On GingerClone I haven't had it crash once yet.
***
Oh and I forgot to mention some things. First in Tegrak I set the CPU low limit to 200mhz and the governor to performance. Makes a HUGE difference in quadrant score and minimal effect on battery life.
Kj2 deodexed and rooted.
Stock browser, Gallery, and recently, Defender 2 cause it to lock up.
Stock browser and Gallery lock up less than on kg2 deodexed/rooted, but still do.
Gallery only on loading, and browser on scrolling.
I had that issue allot then I make it an effort to wipe the cache in recovery once per week, fixes its wagon for me. I also a running back to basics and dealing with the touchwiz launcher. Sacrificing looks in the name of this thing working properly is the name of the game.
Sent from my SGH-T839 using XDA
Dr.Gonz0 said:
I had that issue allot then I make it an effort to wipe the cache in recovery once per week, fixes its wagon for me. I also a running back to basics and dealing with the touchwiz launcher. Sacrificing looks in the name of this thing working properly is the name of the game.
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
Just wipe cache, or wipe cache and dalvik cache?
Hey guys,
My HOXL is currently running ViperXL 2.20, the Beast Mode Kernel at 1.8ghz and -25mv undervolting, sweep2wake and sweep2unlock enabled, as well as aznrice's audio mods. (VooDoo Mode). I'm using the SIO scaler and the smartassv2 governor, occasionally intellidemand.
The thing dun lags. It's slow, unresponsive, choppy. It seems as though my free ram gets eaten up rather quickly, but I get general lag even when it's empty. I don't use any task killers either, I let android take care of that part.
I get wake lag, homescreen lag (Apex Launcher Pro), lag when launching apps, lag while scrolling through apps, just lag. My quadrant is great, in the upper 5000 range, but that doesn't reflect real world performance at all.
It seems as though the lag comes and goes. One minute it'll be fine and fairly responsive, and the next minute it won't. It's usually the latter though. I've tried clean flashing the rom, no success.
What could be wrong here? I played with the HOX+ at AT&T today and I loved it, but I'm reluctant to buy it because of the T3's horrendous DAC. I was even thinking of just going for a Galaxy Note II, and I hate Samsung.
Thanks in advance.
Buy a new phone when you mess yours up?..where have I read this before......?hmm..I do not get any lag whatsoever on viper. Have you even tried reflashing,changing back to stock,factory reset etc.. are you past your 30 Days...by the way new phones come out every month literally so their will always be one faster. You just seem like the person who switches phones because the phone you have you caused the problems...
WhatTheAndroid? said:
Buy a new phone when you mess yours up?..where have I read this before......?hmm..I do not get any lag whatsoever on viper. Have you even tried reflashing,changing back to stock,factory reset etc.. are you past your 30 Days...by the way new phones come out every month literally so their will always be one faster. You just seem like the person who switches phones because the phone you have you caused the problems...
Click to expand...
Click to collapse
Not quite. The HOXL's measly 16gb of memory is killing me, otherwise I love the phone. I'm just in the position to sell the HOXL for double what I paid, get a new phone using someone else's line (because they don't want to upgrade...lol) and profit The only reason I'm not jumping into this decision is because I'd like to see what comes in the next few months. 64gb is awesome though. I got my HOXL on launch day, so I'm way past the 30 day window. I do realize that phones will just become faster, but I'm not too big on the lag I'm seeing here that often makes the phone unusable. It's pretty bad dude.
I've tried reflashing, factory reset numerous times, nothing. Initially, the phone will be snappy as usual, but over the course of a couple of days the lag just comes back. Then again, I was comparing ICS to the smoothness of JB on the HOX+. This lag I'm getting is just something I haven't seen happen before. What kernel are you using? Governor, etc? OC/UV?
Viper has been pretty zippy for me lately...avoid restore system apps...if you're reporting this after a couple hours of usage...wait a couple days and than report back
omario8484 said:
Viper has been pretty zippy for me lately...avoid restore system apps...if you're reporting this after a couple hours of usage...wait a couple days and than report back
Click to expand...
Click to collapse
I only restore my user apps and data, never the system stuff. This is after a week or two of usage, I started using Viper when it was on 1.2.4 a little while ago. The incremental updates did speed it up a bit, but my phone seems to be "choking" to get things done.
Trust me you'll see another jaw dripping HTC released around April I say it even sooner so if you can wait with your one xl you'll have a very good phone.... The one x+ does seem very tempting though
omario8484 said:
Trust me you'll see another jaw dripping HTC released around April I say it even sooner so if you can wait with your one xl you'll have a very good phone.... The one x+ does seem very tempting though
Click to expand...
Click to collapse
That's why I'm holding off a bit lol. I'm assuming that in the near future, Android will match up to/efficiently use the hardware being delivered, essentially becoming synergistic.
Using viper xl with the total opposite of your experience man, try to flash the elemental kernel. Im using it with noop.scheduler and intellidemand governor with UC to 1,3ghz and it has NEVER, for real,been lagged once
Sent from my HTC One XL
I would not buy anything new right now. Wait until we get a GSM version of the Droid DNA, which makes the One X+ look outdated already.
I was considering that, I really wish att had the DNA.
Sent from my HTC One XL using xda premium
Have you ever been satisfied with the responsiveness of the phone on a stock rom or was it always choppy as you feel it is now?
When it was bone dry stock, it was quick and responsive, felt like JB even. Not so much anymore though.
Sent from my HTC One XL using xda premium
i found at&t stock, debloating it myself with some minor mods to be faster then most of the sense roms i've tried
Hmm i had a bit of lag on viper xl 1.x series then i went cm10 to dirty rom had no speed issues on the aosp side just a bit more battery drain compared to the sense roms but my multitasking is more realistic on the aosp side imo. I would say try cleanrom always loved it for closer to bare bones experience.
Me too
I've experienced the exact same issue, although mine ran fine for the first week or so, and then started taking a ****. Stock stays fast, Viper after the first week or two regardless of kernel and cpu speed starts to lag. I've tried CM10 which speed wise is fine (buggy as all hell for me though, no offence CM dev's.. you need more time/source) and doesn't seem to slow down. So far I've flashed CleanRom and IMO it's night and day compared to Viper. Maybe try that?
Is it just me, or do the JB ROMs, custom, official, just rooted, etc, get less battery life than the ICS counterparts?
I first had a HOX back in July/August, and used only ICS ROMs. So I have a pretty good deal of experience with it, got about 5.5-6 hours of screen on time every single time.
Now, I noticed a drop in battery life on JB when I had an S3, and just hated the drain. I thought maybe it was just ROM related, and moved onto an iPhone.
Now back onto another One X, and it seems like I still get less battery life than when I had ICS, and I use it the same way.
Has anyone else noticed it?
Sent from my HTC One XL using Tapatalk 2
I dunno, I got 6 hours onscreen last night. Just gotta tune it right. And make maps hibernate. That was eating half the battery.
Sent from my HTC One XL
Your battery is probably depreciating and loosing its full capacity.
Probably not JUST you, but from what I've read and experienced you're in the minority. My battery is definitely better on JB.
I've had much better life on JB, at least since I updated the whole phone (not just a JB rom). I can go almost two days without a full charge.
Hmmm, I'll try a different ROM then. And a JB radio.
iElvis said:
I've had much better life on JB, at least since I updated the whole phone (not just a JB rom). I can go almost two days without a full charge.
Click to expand...
Click to collapse
What do you mean "update your whole phone" ?
Sent from my HTC One XL using xda app-developers app
Misterowl said:
What do you mean "update your whole phone" ?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I think he means updated via the stock AT&T ROM, which would include the latest radio.
Misterowl said:
What do you mean "update your whole phone" ?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I ran the 2.20 ruu then flashed the 3.18 ota. Once on that base, I've been super stable with CleanROM and Elemental kernel.
My work phone (my HOX) is running completely stock (has to, effing government policies...) and has had terrible battery life since updating to JB. It seems to mostly be due to maps sucking me dry, which I presume is from Google Now. Maps is constantly waking my device and using whatever data connection it can get, which is why i presume the Now stuff. not sure, seems to be fine when i turn off WiFi, so it seems that the wifi use on google now is problematic. I factory reset the device but seems to still be running the same. I've been losing almost 10% battery an hour when I leave my wifi on with barely any use of the phone . this was never the case when the phone was on ICS. it's clearly some sort of data connection as it relates to Maps usage as i've been seeing high CPU usage by the app and, at times, nearly 50% of my battery life going to the maps process.
Also, just noticed on BBS that the android OS and maps high battery usage may be due to alarm manager...I'm seeing many long awake times for a number of apps. hadn't noticed it as much before because i had booted the device multiple times today. any thoughts here? i know what this app is for and there's lots of info and complaints out there about this process on other phones in the past, but not much for stock JB on the HOX...
I have had TERRIBLE battery life while running Sense JB ROMs, (seriously, incredibly bad), versus ICS ROMs. Tried nearly every Sense JB ROM that's out there and countless different radios. No idea why I'm having this problem. I'm not having problems with wakelocks BTW
It's maps. I don't have Google now and maps still ate half my battery on JB. Only way to get around it is make maps hibernate I've found, but this requires rooting.
Sent from my HTC One XL
Try Greenify. You need root, but it allows you to stop apps from running in the background. It's not a task killer, which are worse than nothing because they run constantly shutting down apps that keep restarting; rather, it uses system settings to prevent them from starting background at all. You can use it on stuff like Maps if you use another app to convert them to user apps. I've been using it a couple of weeks, and it's worked just great.
ECEXCURSION said:
It's maps. I don't have Google now and maps still ate half my battery on JB. Only way to get around it is make maps hibernate I've found, but this requires rooting.
Sent from my HTC One XL
Click to expand...
Click to collapse
iElvis said:
Try Greenify. You need root, but it allows you to stop apps from running in the background. It's not a task killer, which are worse than nothing because they run constantly shutting down apps that keep restarting; rather, it uses system settings to prevent them from starting background at all. You can use it on stuff like Maps if you use another app to convert them to user apps. I've been using it a couple of weeks, and it's worked just great.
Click to expand...
Click to collapse
Thanks. It definitely seems like Maps is the problem for me. BBS shows a number of maps-based apps with long wake times. I charged up to about 95% before bed last night, and am going to let it run down all the way today to see what happens. Will post some screenshots later, if anyone cares.
EDIT: Nevermind, will probably post this in the BBS thread, unless anyone here really wants it.
Hydromea said:
I have had TERRIBLE battery life while running Sense JB ROMs, (seriously, incredibly bad), versus ICS ROMs. Tried nearly every Sense JB ROM that's out there and countless different radios. No idea why I'm having this problem. I'm not having problems with wakelocks BTW
Click to expand...
Click to collapse
Serially doubt you've tried viper xl
Sent from my HTC One X using xda premium
Hydromea said:
I have had TERRIBLE battery life while running Sense JB ROMs, (seriously, incredibly bad), versus ICS ROMs. Tried nearly every Sense JB ROM that's out there and countless different radios. No idea why I'm having this problem. I'm not having problems with wakelocks BTW
Click to expand...
Click to collapse
Same. 2.5 hrs of screen time vs 3.5 for ICS. Same usage.
Viper JB vs Cleanrom ICS.
Stock everything else (radio, kernal)
maybe not necessarily maps like originally thought, though it's one of the culprits. the mediascanner just happens to hit maps a lot, likely due to it's typically-large cache. check this thread, particularly post #42 and the Google response another 10 posts or so later. sounds like there is definitely an issue with the device indexing and it's the same thing that affected a number android devices. my guess is that some people just dont have a lot of media files (or wipe their phones often enough that they dont accumulate much) and dont see as much of the effect.
https://code.google.com/p/android/issues/detail?id=37199
there's also a link at the end of that thread to another similar thread, found here: http://code.google.com/p/android/issues/detail?id=40370#58
i guess we really need to get that 4.2 source. also looks like someone built a sort of patch into CM10 on teh SGS3, but i dont know those forums well so i can't corroborate this. wow, i just ****ing said corroborate, time to go to bed.
Lol, corroborate.
Idk, I still think it's maps. I don't have very much media (2 albums) and disabling maps fixed my battery life (200% improvement, literally).
Sent from my HTC One XL
ECEXCURSION said:
Lol, corroborate.
Idk, I still think it's maps. I don't have very much media (2 albums) and disabling maps fixed my battery life (200% improvement, literally).
Sent from my HTC One XL
Click to expand...
Click to collapse
yeah, i'm back on this boat as well. maps still has a long wake time i'm seeing location scanner services running so i'm thinking it's a location-based thing. going to let my phone die today so i can get a good BBS log since i screwed that up yesterday. i'm noticing odd dips in battery life whenever the phone wakes up. it seems to stay awake for up to 10-20 mins, but with the screen off. really weird thing is that when i let it sit overnight, there's no spike (just greater than usual battery drain) but it's when the phone first wakes up that it seems to be really draining and staying awake.
I have a Sensation 4G running Android Revolution HD 6.7.2 (bought used, came with, never changed it). I'm generally pretty happy with this situation, but there are two specific situations where it just slows to a crawl. As far as i can recall, it's always been this way for these two situations. (I've been using the phone with this ROM for about a year.)
The first situation is when I install any new app or even an update for an app. For several minutes after that, everything is very sluggish. I can still use the phone, but it's a huge pain. This is true whether or not I try to use the just-installed app or update. My best guess about this (and it's only a guess) is that the slow-down is due to populating the Dalvik cache for the new/updated app. Still, that seems like it ought to be a background thing with only minor impact on foreground performance.
The second situation is when I run the Chrome browser. Other browsers (native, FireFox, Puffin) are just fine. When I run Chrome, things really, really, really tank. When I use the developer option to overlay the load average on the screen, I've seen it go as high as 65. I don't care what kind of phone hardware you have ... if your load average is 65, you are not having a good day. Anyhow, things stay zonked pretty much forever, even if I don't actually do anything in Chrome, and even if it's in the background. I've waited literally hours hoping that something just had to "settle", but no luck. I often resort to a battery pull after Chrome experiments because it's too sluggish to wait for the power button long press. (I have Chrome on a couple other mobile devices, and it behaves just fine there.)
Anybody got any clues about things for me to try to alleviate by undeserved suffering?
wjcarpenter said:
I have a Sensation 4G running Android Revolution HD 6.7.2 (bought used, came with, never changed it). I'm generally pretty happy with this situation, but there are two specific situations where it just slows to a crawl. As far as i can recall, it's always been this way for these two situations. (I've been using the phone with this ROM for about a year.)
The first situation is when I install any new app or even an update for an app. For several minutes after that, everything is very sluggish. I can still use the phone, but it's a huge pain. This is true whether or not I try to use the just-installed app or update. My best guess about this (and it's only a guess) is that the slow-down is due to populating the Dalvik cache for the new/updated app. Still, that seems like it ought to be a background thing with only minor impact on foreground performance.
The second situation is when I run the Chrome browser. Other browsers (native, FireFox, Puffin) are just fine. When I run Chrome, things really, really, really tank. When I use the developer option to overlay the load average on the screen, I've seen it go as high as 65. I don't care what kind of phone hardware you have ... if your load average is 65, you are not having a good day. Anyhow, things stay zonked pretty much forever, even if I don't actually do anything in Chrome, and even if it's in the background. I've waited literally hours hoping that something just had to "settle", but no luck. I often resort to a battery pull after Chrome experiments because it's too sluggish to wait for the power button long press. (I have Chrome on a couple other mobile devices, and it behaves just fine there.)
Anybody got any clues about things for me to try to alleviate by undeserved suffering?
Click to expand...
Click to collapse
Hi,
6.7.2 is quite old ,now.
Have you considered upgrading?
7.3 has just come out,with very few problems reported.
What does your bootloader say?
malybru said:
6.7.2 is quite old ,now.
Have you considered upgrading?
7.3 has just come out,with very few problems reported.
What does your bootloader say?
Click to expand...
Click to collapse
Long ago, on another phone, I was one of those guys who regularly flashed ROMs in chase of ... something (I forget what ). Now, I'm just a guy who wants to use his phone every day with the zillion little application customizations and preferences and whatnot. If I decided to endure the pain of setting everything up again (and I'm probably exaggerating that pain in my brain-pan), I'd probably just flash back to stock. Although the ROM might be the problem, the specific nature of the two problems makes me hope/think/wonder that it might be just some setting somewhere that needs a punch in the arm.
Thanks for the suggestion though. Maybe I'll go poke around the changelogs for Android Revolution and see what's to see.
wjcarpenter said:
I have a Sensation 4G running Android Revolution HD 6.7.2 (bought used, came with, never changed it). I'm generally pretty happy with this situation, but there are two specific situations where it just slows to a crawl. As far as i can recall, it's always been this way for these two situations. (I've been using the phone with this ROM for about a year.)
The first situation is when I install any new app or even an update for an app. For several minutes after that, everything is very sluggish. I can still use the phone, but it's a huge pain. This is true whether or not I try to use the just-installed app or update. My best guess about this (and it's only a guess) is that the slow-down is due to populating the Dalvik cache for the new/updated app. Still, that seems like it ought to be a background thing with only minor impact on foreground performance.
The second situation is when I run the Chrome browser. Other browsers (native, FireFox, Puffin) are just fine. When I run Chrome, things really, really, really tank. When I use the developer option to overlay the load average on the screen, I've seen it go as high as 65. I don't care what kind of phone hardware you have ... if your load average is 65, you are not having a good day. Anyhow, things stay zonked pretty much forever, even if I don't actually do anything in Chrome, and even if it's in the background. I've waited literally hours hoping that something just had to "settle", but no luck. I often resort to a battery pull after Chrome experiments because it's too sluggish to wait for the power button long press. (I have Chrome on a couple other mobile devices, and it behaves just fine there.)
Anybody got any clues about things for me to try to alleviate by undeserved suffering?
Click to expand...
Click to collapse
The first issue is because of our slow internal memory. The stall happening when updating/installing an app is because of long I/O waits it probably might happen over other custom roms you try here too but not as long as you said.. I used to have sluggish behavior couple of seconds after app installation (max 10 seconds). Now the only roms which were able to bypass this issue were the sense 4+ jellybean roms viz revelation / viperS 3.1.0 roms. If you want to prevent this annoying issue then change to either of those above roms.. Somehow jellybean roms were able to keep those I/O waits less.
Now to the second issue.. Sensation by default has less ram (yes 768 MB is not enough for ics/JB roms). Now when you fill your device with apps due to true multitasking nature of the Android lots of apps keep on running in the background (even restarting by themselves when killed). And Chrome is one Ram eating b***h it at least needs 50MB of memory (where other browsers like dolphin browser can run smooth over 20MB ram) so it's always slow for me takes ages to open up properly. So my suggestion is switch to different browser or install an app called "greenify" (rooted app.. You need to give root permissions) . The advantage of using this greenify app is it can hibernate persistent apps.. Thus giving you enough ram and battery. Greenify is one acclaimed rooted app which does what it says. Try it and see how the device is doing after this
Sent from my HTC Sensation 4G using xda premium
FWIW, I decided to take the plunge and upgrade to the latest ARHD. At first glance, it seems to have dealt with these two performance items. However, I'm still installing/configuring some of the assorted junk I had before. I'm on the lookout for the one thing that clobbers me and will report here if I find such a thing. (I'm also working through a couple of FCs of system stuff, but that's not for this thread.)