Database Info

[Q] Frequent launcher freezes

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

Phone continues to randomly reboot even with new radios

I have tried 4 different radios and this phone still randomly reboots with frequency. I am the the 802 radio and it seems even worse then earlier radios. I am currently on gingerritis rom which i installed yesterday and have probably had 12 reboots since then.
Is it a combination of the rom and radio, or does just the radio make the phone reboot? I am really just tempted to flash it back to stock, sell it with the warning of this phone enjoys random reboots and get another phone.
while i typed this up it just rebooted twice on its own

I dont think the radio is what is going to fix the reboot issue. I know for some of the roms the fix was flashing the ziggy kernel.
Maybe give that a shot.

brownsfan said:
I dont think the radio is what is going to fix the reboot issue. I know for some of the roms the fix was flashing the ziggy kernel.
Maybe give that a shot.
Click to expand...
Click to collapse
If hes using gingeritis, hes already using ziggy's kernel. Sounds weird i know, but try a new battery
Sent from my TBolt using my f***king thumbs...

i think overclocking to high and all the kernel cpu mods are whats causing this, not the radios.

fixxxer2008 said:
i think overclocking to high and all the kernel cpu mods are whats causing this, not the radios.
Click to expand...
Click to collapse
I agree. Ziggy's stock voltage settings are very conservative north of about 1.5GHz. If you're tweaking it, definitely pay attention to the voltage.

nope not touching voltage or overclocking, i just put rom on thats about as far as i go tweaking phone.
Installed M0N0LITHTH3ORY rom and so far no reboots today, the gingeritis one must hate my phone cause in the less than 24 hours it was on the phone damn thing rebooted easy 10 times. But now this one is giving me some unexpected errors with weather app. I will give this one a week and see how it does and if no good on to next rom i guess.

-magnum- said:
nope not touching voltage or overclocking, i just put rom on thats about as far as i go tweaking phone.
Installed M0N0LITHTH3ORY rom and so far no reboots today, the gingeritis one must hate my phone cause in the less than 24 hours it was on the phone damn thing rebooted easy 10 times. But now this one is giving me some unexpected errors with weather app. I will give this one a week and see how it does and if no good on to next rom i guess.
Click to expand...
Click to collapse
Have you ever formatted /system?

yeah every time i put new rom i go into clockwork recovery
i wipe / factory reset
then format /system /cache /data
and wipe davlik cache
then install rom

double post...

i know my phone didnt like a few different roms. try a diffeerent one. also try doing each step 3 times. i did that after my phone rebooted on an a0sp rom by droidtheroy, after that it worked just fine on the rom that was rebooting

You know what? I was having the same problem and tired as hell of my TB. I was so tired of the little problems and the large rebooting problem that I had learned to really hate this phone.
A few days ago I decided to just use the new leaked, stock, unrooted, GB 210 RUU and give that one more try before I either took a hammer to this phone or unrooted and tried to get VZW to replace it.
I've had the latest leaked RUU on this phone for a few days now and I'm loving it again. Yeah, stock, unrooted, but also super fast GPS locking, fast 3g/LTE switching, no more reboots, not one. Battery is actually not bad at all after turning off a few of the stock bloat like Blockbuster. The gui is fast and smooth, I can't say whether or not it is as fast as it was when I was running custom ROMs but as far as I'm concerned its a big who cares. I now have a nicely working phone again. This is just my experience and my opinion, YMMV!
R

-magnum- said:
I am currently on gingerritis rom which i installed yesterday and have probably had 12 reboots since then.
Click to expand...
Click to collapse
I got reboots with gingeritis and liquid ROMs, I've had no reboots in a week now running Virus' Synergy ROM. Try a different ROM, it should fix your problems.
Here's a link to Virus' work:
http://forum.xda-developers.com/showthread.php?t=1003891

Second the ROM recommendation. Try a different one. I had the same issue with wanting to grenade this thing until I found a combo of ROM and radio that was stable for my use and applications.
Now I wouldn't think of tossing this phone.
Sent from my ADR6400L using Tapatalk

Stability and battery life good for me with stock 1.70.605.0. Currently at 868 hours uptime.

yeah i am on monolith rom and so far no reboots, i am going to give this one a shot for now, hopefully this cures it.

[Q] [SOLVED] Random shutdowns / turning off.

Hey guys,
The topic of this thread has change slightly since I started it. Please disregard the first few posts after this one.
The problem is that when I install a new ROM, it works perfectly for an hour or perhaps even the day, and then I start getting random shutdowns. These seem to start out of the blue and I cant work it out.
When installing a new ROM, I always check the MD5 and perform a superwipe before starting to use the ROM. Ill put back a few apps using titanium backup pro.
I don't use any hacked apps or task killers.
I have searched but cant find anything useful.
Currently using Insertcoin Sense 4 RC5. Firmware 3.32.
I have tried three different kernals (Bricked, Sebastian and RCMix), all with the same problem.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz with max screen off at ~500Mhz. Seems stable for now, been running 24hrs - no restarts.
This is interesting because I had a GB Rom running at 1.5Ghz with no problems, maybe its something to do with ICS.
Any ideas?
[SOLVED]
Sent the phone off to htc and they have replaced the motherboard. Its all fine and dandy now!
They dont know why it happened or how to avoid it in the future...useful, but if you're still in warranty then send it off, it took exactly a week to get back to me (Monday to Monday). Good luck!
Max

Well no need for factory reset. Superwipe? Yes.
What roms cause this?
What firmware is ur senny on? Ex: 1.17? 3.24?
Phone have physical damage?
Has it been wet?
Sent From Space Using My ICS Flavored Sensation

Thanks for your reply.
No, the phone is basically new, but as I said this has happened before.
Running this ROM on 3.24:
http://forum.xda-developers.com/showthread.php?t=1468683
But this does happen on other ROMS too, they work perfectly for a while and then slowly begin to develop problems. At this stage I usually install the latest version of the ROM but I'm actually happy with the ROM at the moment and dont want to have to keep changing it!

I've been running Darkforest ROM since early stages and have had no problems so far. Maybe try that one. It's on v 5.1.5 now and it's very fast and very stable, moreso than many other ROMs i've tried.

Could be a defective device possibly? Are u using the kernel that comes with the rom?
Sent From Space Using My ICS Flavored Sensation

I would download 1-click cleaner and clean the cache every week. Also you might want to boot into recovery and wipe cache and dalvik cache every two weeks.
Sent from my HTC Sensation 4G using XDA App

I dont think there is anything wrong with the device, I'll try wiping the cache's and see if that makes a difference. Thank you very much for all your answers so far.
Max

Could possibly be an app try removing all your apps and install 1 by 1 give it a couple of weeks see if it happens again, I got a problem from juice defender pro (payed for) worked alright for few days then my launcher started force closing all the time took me ages to figure it out but got there by removing all my apps and installing them 1 by 1 long and time staking but worth a try
Sent from my HTC Sensation Z710e using xda premium

Okay well ive tried clearing the cache and davlik cache with no luck, less restarts but they are still there. I am resistant to start removing apps as I use them on a daily basis. Before I try this, does anyone have any other ideas?
Thanks,
Max

I have the same problem :/ it happens in both GB and ICS but It never happened to me till about 2 or 3 months ago
Sent from my HTC Sensation Z710e using xda premium

This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble

darksupernova said:
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
Click to expand...
Click to collapse
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio

ardom said:
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
What other information would you like?
I think it may be a kernel issue, I'm going to try a few...
Tried three different kernals now, all with the same problem which would indicate its not a kernal problem? Something else perhaps? (Tried bricked, sebastian and RCMix)

its not a problem, its with network connection
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.

Danyal93 said:
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Click to expand...
Click to collapse
Pretty sure its a power/bat problem for me.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz
Any ideas?

Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!

Having EXACT ones you are having. Buy another battery if that doesn't work its a hardware problem. I still need to buy my battery but will post and let you know if it worked.
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
darksupernova said:
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Click to expand...
Click to collapse
I'm also starting to think its caused by not letting the battery fully die and recharging it a lot but that's just my guess?

I switched back to gingerbread yesterday and so far I've had no problems which would indicate its not a hardware issue...? Usually by now I've had a few shut downs..

So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do

sickorwuut said:
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
Click to expand...
Click to collapse
Yeah the problems started again for me on gingerbread. I've read its a motherboard problem I think I'm gonna have to send it off to HTC... Great... 3 weeks no phone...

Issues with AT&T RUU_Evita_UL_Cingular_US-1.82.502

Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.

gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2

gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Wowsers! That's good to know. I haven't updated yet as I'm on Rogers, but I'll keep that in mind when a Rogers version comes around.
As for the WiFi issue, I've had it the whole time. I went 9 days before rooting, and it's been maybe 15 days since I rooted. It existed pre- and post-root for me.

mobilehavoc said:
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Mine seems to be running at 1.5ghz fine. I'm on the new version. I smell FUD.
Sent from my HTC One X using Tapatalk 2

same as above, no issues here.

Also have the update no issues
Sent from my HTC One X using Tapatalk 2

I went from the full detox to 1.82 and after start up i ran both quadrant and antutu benchmarks. I noticed that quadrant score was only 4k when it used to be 4.5k. antutu was also lower and thats when I noticed the clock speed being listed at 1243 mhz (something around there). I downloaded the antutu cpu master free and it allowed me to move the slider back up to 1512 mhz.
Only sharing what I expierenced, now i'm trying to go back to 1.73 and having trouble...seems like it doesn't want me to move back down.

gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.

cloudraker said:
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.
Click to expand...
Click to collapse
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?

gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Im guessing that like the only other HTC phone ive owned, downgrading wont happen without s-off. So the only thing i can suggest is to instead try going back to 1.82 and get the phone functional so at least its not a brick and if its still showing an incorrect clock speed maybe you can get an exchange.

gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Yea you can't go back down.Have to wait for the official ota and see if its any different.

My phone runs much smoother with the new update...almost like a different phone. I could care less what the benchmarks say...I'm a real world guy.
Sent from my HTC One X using Tapatalk 2

I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.

1.73 here...
5,013 -- Quadrant Standard
So perhaps something is just wrong with you're phone. Also, I thought you couldn't modify your clock speed without unlocked bootloader + root/s-off or whatever. I know the basics, Just not the full technical explanation of it all. Sounds to me like you have a problem though from the beginning to have <5K of a quadrant score.
Just removed everything I dont need. De-oxed and removed bloatware + added a couple games. Cleared "multi-tasker" and used task manager [not the stock] widget to free up memory... Which made it go to 4,760. So doing all this stuff to "help" somewhat backfired. Im wondering if its the task manager widget/app always running :b Idk. Point is, I think its your phone. Even if i'm not at 1.8~.

gtung99 said:
I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.
Click to expand...
Click to collapse
good to know. and FYI, though it's not my forte, i was reading either the "Update 1.82" thread or the thread with the title named the same as the 1.82 patch (can't recall which one) and I remember someone mentioning that to roll back to 1.72 after upgrading, you need to edit a certain .apk file, which, if done improperly, will totally brick the device. glad you were able to get 1.82 to run properly. I've decided to wait for the full OTA from ATT since my wi-fi issues are generally minimal.

Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.

ThisWasATriumph said:
Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.
Click to expand...
Click to collapse
The IO score is lower now. Can't wait until Franco or someone else releases some kernels that will really make this phone rock. I had a galaxy nexus before with the stock rom but running Franco latest kernel that boosted the Quadrant score from 2200 to 3600. Mostly it was due to enhancements that dramaticlly increased memory and IO performance.

I installed the leaked update and my wifi still doesn't work right. It is extremely slow and crashes my entire network and brings it to its knees. Wifi will not work on a single device when my one x is connected to my wifi network. Ideas? Has anyone else experience this?

I hadn't thought of this being the cause but I have noticed that my wifi at home, specially when watching netflix is way slow. I always have my wifi on my HOX turned on when at home. I'm on 1.82 and running Clean ROM 2.3. Are you saying that this could be causing my slowness on all my devices that are also hooked into my wifi at home?

[Q] Why is my HOXL so laggy? (ViperXL 2.20)

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?