Hello everyone,
Has anybody else who updated to 4.1.57 find that their Atrix is now kinda sluggish? I don't mean all the time, but every now and then I get random stutters or sluggishness when switching between programs. A couple of times, it even screen locks for a few seconds when waking up. This has never happened to me before with the 4.1.26, where programs just run without hesitation. They either run smoothly, or FC in the process. But now, some of them just becomes jittery.
I wonder if it has something to do with Motorola's battery improvement in the update. When it got sluggish on me, I decided to go to into setcpu to see at wat speed the phone was running. I noticed that the phone was throttling severely all the way down to 216 mhz the second the phone is not being used. it fluctuates up and down but it seems to always drop down there once i dont touch the phone. I think this is causing an issue cuz there's a lot of background apps and widgets running and once you try running an active program, it takes a split second to start, and that split second causes it to stutter.
I haven't had the screen lock in a while, so that's a good thing. But it seems setcpu can't seem to force the cpu to constantly stay high, even if i put the minimum to 1000mhz, so I get those stutters every now and then.
Anybody has any suggestions on this matter? Im thinking if this persists, I might just go back to 5.1.26 until they come up with a major update. Really the only reason I updated was cuz the prompt was driving me mad.
p.s. another way I know how the cpu isnt running a constant 1ghz --- my phone isnt as hot as it used to be. it used to be so warm in my hand, my hand would turn red from holding it.
It takes very, very little time for a modern CPU to change its clock speed. Monitor your computer's CPU clock closely sometime, it almost certainly does throttling to a similar degree. I also observed similar levels of throttling via tegrastats on my Atrix prior to the update.
Personally 1.5.7 has been good for me, at least in the sense that nothing appears to be worse after.
Sent from my MB860 using XDA App
Only heard good reviews on 4.1.57. Can't wait for Bell to issue it too
lol, i dont like throttling. All my PCs n laptops run on full speed (throttling disabled) whenever they're on. I expect the same with my phone x) I just don't like any lag but I understand wat you mean. I still wanna hear what other's feel about the update.
note: I'm about to deodex the phone in a bit. Let's see how it ends
Moving stuff around in device memory is an order of magnitude slower than your CPU changing clock speed, and moving stuff between flash and device member is an order of magnitude or two slower than that. CPU throttling isn't the right place to look for this sort of issue.
As for your computers and not allowing them to throttle...enjoy the power bill I suppose. Even in overclocked scenarios modern processors work just fine with throttling enabled.
Sent from my MB860 using XDA App
Atrix 4.1.57 issues
I have had my Atrix for over a month with no issues. After the 4.1.57 update I have the following 3 issues:
1. The phone randomely reboots (never did this before the update)
2. The cell signal is much weaker; no signal in areas where it had signal before
3. Apps seems to start slower.
I called motorola technical support and asked if there is a way to un-install this update; the answer is NO, all they can come up with is a factory RESET which will not remove the update but will remove all my data and Apps.
I finally sent the phone to AT&T and got a replacement with 4.1.26 and it works fine, especially the battery life and the cell signal and no reboots so far.
Related
I apologize now for the long explanation but feel the info is needed.
I had a replacement phone in March so I could root and after that all was good, I finally in May got frustrated with my lead bunker of a house and no cell signal so I got a Verizon Network Range Extender (Samsung). After I got it and a week of getting it working right my cell signal hasn't been the same, I know the bar graph isn't an accurate representation of the signal so I was watching the Db levels and the fact when I was in the middle of town in the open I had one or no bars and a -104 signal.
After Kaos and Conap got Froyo up and usable I tried using the ROM's but after a week the phone would be so unresponsive it would take literally 5 minutes to find a number and dial it. I would miss calls all the time and constantly would have to reboot. I was at first trying 768 on the OC but eventually stepped it down to 710. I have tried KaosFroyo V19-33 with no luck, each update I do has less and less time between flashing and when it becomes unresponsive. I have Tried CLEB 1.6-2.4 same thing. The only ROM that I can use with the best results is Plain_JaneT2 OC'd at 710.
I currently still have cell reception issues and sluggishness on most ROM's, I am on the current 4.27 radio and have formatted several times the SD card to start with a blank slate. I am not using swap or ext3 for AP2SD. I have unrooted and rerooted 2 times. This phone was pre legit 2.1 OTA.
Not sure what I did or what to do next to get it back in order
morphius2036 said:
I apologize now for the long explanation but feel the info is needed.
I had a replacement phone in March so I could root and after that all was good, I finally in May got frustrated with my lead bunker of a house and no cell signal so I got a Verizon Network Range Extender (Samsung). After I got it and a week of getting it working right my cell signal hasn't been the same, I know the bar graph isn't an accurate representation of the signal so I was watching the Db levels and the fact when I was in the middle of town in the open I had one or no bars and a -104 signal.
After Kaos and Conap got Froyo up and usable I tried using the ROM's but after a week the phone would be so unresponsive it would take literally 5 minutes to find a number and dial it. I would miss calls all the time and constantly would have to reboot. I was at first trying 768 on the OC but eventually stepped it down to 710. I have tried KaosFroyo V19-33 with no luck, each update I do has less and less time between flashing and when it becomes unresponsive. I have Tried CLEB 1.6-2.4 same thing. The only ROM that I can use with the best results is Plain_JaneT2 OC'd at 710.
I currently still have cell reception issues and sluggishness on most ROM's, I am on the current 4.27 radio and have formatted several times the SD card to start with a blank slate. I am not using swap or ext3 for AP2SD. I have unrooted and rerooted 2 times. This phone was pre legit 2.1 OTA.
Not sure what I did or what to do next to get it back in order
Click to expand...
Click to collapse
i cant attest for the network extender but i have noticed if the rom has an overclocked kernal and i use setcpu it turns into a slugg real quick especially with autokiller installed. u might just try a rom and not overclock it and and uninstall autokiller that is if you have that..
Are you using the setcpu widget? That messes things up quite a lot. The degradation in performance is enough that you'll have to pull the battery waking up, even when you're overclocking to 768mhz.
No I never use that I just go on the hopes that the OC is working but I wasn't aware that the OC Kernel and the Autokiller was an issue. May give that a try.
Usually the sluggishness is there but not terribly bad but I am lazy after I flash a new rom and don't set up my screens or apps for a couple of days so that may be the reason there is a window of time that the performace isn't teribble and tollerable but as soon as I do a SetCPU it goes out the window.
Thanks for the advice, just wish you had something for my cell signal.
I don't know about the extender. But yeah don't use the widget. What settings do you use for SetCPU? You may want to call Verizon for the extender.
Ok so day 2 of CELB 2.6 and all is good I didn't go to SetCPU and I noticed when I put the Facebook widget on the screen things got somewhat slow so I took it off. Still have some slow response in the app drawer but that may be from my screen replacement. It is a Verizon screen not a third party but don't know.
As for signal I am just going to suck it up and wait till August and get a newer phone.
Thanks for all the ideas
I would remove setcpu altogether and maybe try a different rom just to be safe.
Sent from my BLACK RAIN V2 using Tapatalk
I wanna know if anyone else has this issue or not when click an app like a game it takes up to 10 seconds for it to run and after exiting sometimes the main screen is very delayed and sometimes unresponsive when scrolling left and right. I also have an issue of the phone not wanting to switch back to 4g if in 3g or 1x just stuck until I reboot or restart it. Wanna know if I should get this one replaced or not. Also GPS is horrible never accurate. It say in running little kids on the sidewalk over constantly or running threw people house. I have factory data restored it but same problem. Need to know if I need new one?
Zinsko said:
I wanna know if anyone else has this issue or not when click an app like a game it takes up to 10 seconds for it to run and after exiting sometimes the main screen is very delayed and sometimes unresponsive when scrolling left and right. I also have an issue of the phone not wanting to switch back to 4g if in 3g or 1x just stuck until I reboot or restart it. Wanna know if I should get this one replaced or not. Also GPS is horrible never accurate. It say in running little kids on the sidewalk over constantly or running threw people house. I have factory data restored it but same problem. Need to know if I need new one?
Click to expand...
Click to collapse
It does happen. Try a different kernel or over clocking.
this happens to me occasionally, usually only when the battery is hot/doing a LOT of things at once. (meaning when i'm charging and using pandora over bluetooth, wireless tether, and waze at once) the phone lags up so much that when i press the home button, the haptic vibrate stays on for about 3 seconds.... this is when i know that its happening - and i'll just pull the battery...
If you're running stock & it's been like that since day one, you might consider exchanging it. If you're running a custom rom/kernel, reflash & leave it at default settings for a few days & see if the problems resolve
Sent from my ADR6400L using XDA App
I've never had the lag issue you speak of, however, the gps issue I have seen, but has been fixed in recent custom roms and will be addressed in the update. If you are on stock, you might want to just wait it out for 9 more days till the OTA rolls out. If you are using a custom rom/kernel combo, what are you using?
sublimaze said:
If you're running stock & it's been like that since day one, you might consider exchanging it. If you're running a custom rom/kernel, reflash & leave it at default settings for a few days & see if the problems resolve
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
+1
I also forgot to mention that i'm on BAMF 1.8 with the kernel that it comes with.
If your rooted, i'd recommend unchecking your "set at boot" and profiles in SetCPU, reboot, and see if it continues. As said above, if unrooted... a call to verizon may be in order.
My phone is not rooted every phone I have rooted besides like 2 I have bricked. But yeah I don't get why they didn't run this stupid phone a dule core. I got to play with a phone that had a dule core and response is so amazing.
Then you should take it back to verizon & exchange it for another. Your Tbolt shouldn't be like that out of the box. I've never had GPS issues, even on stock it would lock within a few seconds. And dual core is overrated unless you have apps that actually take advantage of it (not many). No wonder you were impressed with dual core phones lol. My mildly overclocked Tbolt runs Sense just as fluidly as any Atrix runs MotoBlur
Sent from my ADR6400L using XDA App
Okay thanks I have been looking for an excuse to tell them basterds off.
So, I have one of the first Vibrants to hit the store. I'm running Neobuddy ICS Passion V8. Before the *****ing begins I want to say that I love this rom.
I followed the install instructions to a "T".
I used antutu cpu master to overclock to 1.3 because I read that other people were doing it and didn't see any complaints. When my phone booted to the point where the message that cpu master had superuser privileges came up, it froze and the display changed colors getting lighter and washed out looking. That scared the crap out of me and I thought I had just cooked my cpu. I pulled the battery and rebooted then tried to open the app and change the settings before it froze and failed, rebooting 6 times, battery pull each time. I finally relented and did a factory reset. Previous to this adventure I had it clocked at 1Ghz max and 100 min and was experiencing no lag. I just got greedy. I only changed it at all because I was getting 16 hours of battery life and thought I could trade some battery for speed. I have it running at 1.2 now and it's fine. So this is not so much a question but an answer to anyone who might be asking themselves if they should overclock to 1.3.
Bugs
mute/unmute necessary for incoming call audio
automatic brightness not responsive
complaints
contacts app doesn't match the rest of the theme
no text button next to phone button on contact
no long press functionality on contact
When it comes to Vibrants, all our phones are different. Some users will be able to run at 1.3 from now until our Zombie overlords take over and we're forced into indentured servitude. Others, like you and I will be lucky to run a mild OC without freezes.
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
What he said!
younix258 said:
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
Click to expand...
Click to collapse
My first Vibrant T959, manufactured prior to Oct 2010, used to fly, and overclock like there wasn't any tomorrow, and would flash anything! Was the most cooperative phone I ever had! Wish my wife was like that. LOL
Then I unfortunately got into a true HardBrick with it, and stupidly, instead of JTAGing it, got T-Mobile to exchange it, for a same model, but with a manufacturing date on it of 8-2011!
And this replacement phone, hasn't even ever performed as well as the old one, despite how I set it up, And at first it was stuburn as hell to get it to cooperate with flashing, until I unlocked it, and it calmed down alot, even though that makes no sense at all, but nun the less, it is what it is!
Point is, that each week, month or quarter, the phones aren't consistent in manufacturing qualities or how they run and perform, or the components they use. I had a Thoroughbred in the beginning, and now I how a plow horse, yes she still works well, but needs alot of coaxing, I had to re-do the GPS contacts right so there was firm pressure, and the SW flashes were a ***** in the beginning!
But I believe when this phone first came out, there was better quality of manufacturing and they used the same consistent components, until they shifted their focus on other models to push onto the market!
So again, what Billy Bobs got going with his, Isn't what it ll be with yours!!
I'm running JT's vanilla GB [over Heimdall'ed stock EH03] on my fascinate.
I use my fascinate as my alarm clock, and I woke up this morning to a extremely choppy ringtone. < and that is is the understatement of the day.
Anyway, I try to press "dismiss" to dismiss my alarm, and it feels like the screen is not responding. I press the power button, and it takes probably like 5 seconds to complete the CRT animation. After that, I can see the screen is still on (hard to tell unless in the dark with the AMOLED), and it won't do a thing after that until I 3-button-combo or take out the battery.
As a side note, it was also doing this on my previous rom, SuperClean3 v8.1. One of the main reasons I switched back to JT's vanilla gb.
The first night the alarm worked fine. [2 days ago] Yesterday, I was watching some video files, I pressed the power button, I left for a few minutes, I came back and it was frozen. [Took foreverrrrrr for the CRT turn-on animation, and screen did not respond].
This is really really annoying, and I would really like to find out what is wrong with my phone.
One more thing I should mention.. this same kind of thing happened once in a while on the stock froyo firmware, when I bought it on craigslist. I would come to it sometimes and turn it on, and the lockscreen would show and the touchscreen wouldn't respond. I had to take the batt. out then cuz I didn't know about 3-button-combo.
The USB would only charge and not transfer files and only would charge.
So I sent it in cuz samsung said I had 1 mo. warranty left, and then they said they fixed everything in the ticked, and I got it back and it seemed to work. [the usb file transfer worked..]
So can anybody give me any advice? Like logcat? Would that tell me what is causing this problem?
Any help is appreciated!
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
k_nivesout said:
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
Click to expand...
Click to collapse
Thanks for the reply. I will look into this 'sleep of death' thing.
And I haven't edited my cpu settings. I went to superuser to be sure and the only apps listed are Superuser, Terminal Emulator, and Titanium Backup.
So I just went on a 1-hour trip, and when I got to where I was going, this happened to me again. The screen-on animation was slower than a slug on salt. 3-button-combo reset, I let it reboot, and it was fine.
I just got home 1/2 hr ago and it did it again.
Sigh.. well I only have like 2 apps that always run, 3G Watchdog and Equalizer. I've uninstalled 3G WD just to see if it does anything.
Edit: I will install ROM Manager and set the absolute minimum freq to 200mhz, and see what happens. That would make sense if it's messing up at 100mhz when the screen goes off, and then it's not able to think fast enough to up it back to 1ghz.
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have much expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
k_nivesout said:
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
Click to expand...
Click to collapse
My bad, I meant ROM Toolbox. It has lots of apps built in including a CPU slider. Anyhow disabling 100mhz did not fix anything. So tonight I will set the minimum frequency to 800 or even 1000 mhz because I want to see if that stops the freezing up. If it does, then I'll know it's a clock speed issue.
I should also mention I sent it in for USB repair. It wouldn't connect to PC, it'd only charge. I also mentioned to Samsung it would lock up every so often from waking up. They upgraded froyo to gingerbread and said it passed all tests, sent it back, I never stayed on the firmware they gave me long enough to see if it froze up.
So on the stock roms, do they underclock the cpu frequency by default??
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
k_nivesout said:
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
Click to expand...
Click to collapse
Lol, when I sent it in there was like half a month or so left on the warranty, the person said it expires at the end of this month [Dec] so I figure maybe a day or two.
What's the IRC channel info? freenode?
EDIT: I forgot to ask something. So you are saying, the stock firmware [EH03 or froyo EH09] runs the cpu clock constantly at 1GHz? Even when it's sleeping? Wouldn't that give bad battery life? [lol, speaking of batteries, I just got a new one and it's charging]
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
gotsflat4love said:
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
Click to expand...
Click to collapse
This is bad news indeed, since I am not even sure how many days I have on the warranty. But I think I will Odin EH03, and then set the alarm tonight. If I wake up and it's done it again, I will call up samsung and tell them and hopefully I have warranty.
But please, tell me, when you tried to turn on the phone did the CRT animation go very slowly? and then when you pressed power, it wouldn't come on again?
Edit 2: alright! I call samsung and I have warranty until Jan 9. Woot.. So I set up an RMA with samsung, I will Odin EH03 tonight. If I wake up to a choppy alarm and a non-responsive screen, I shall send it to samsung ASAP and I hope they gimme a brand new Fascinate. that would be awesome..
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
k_nivesout said:
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
Click to expand...
Click to collapse
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
So this morning, I woke up to my iPod's alarm, which I had set as a backup a few minutes after my Phone alarm should have gone off. I went to see if the phone was frozen, like I was hoping, so that it would reliably broken , but instead it was off. I turn it on, it shows the full green battery.. then it boots up like nothing was wrong. But I think that turning off randomly every night [which I assume it should do every time] is enough for Samsung to realize my phone really is screwed and that they need to do something about that.
So anyway, I printed out the label, packed my phone, and dropped my phone off at the local UPS drop off.
Hopefully I will be receiving some good news from samsung soon [i.e. that they will give me a replacement... ]
mvmacd said:
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
Click to expand...
Click to collapse
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
k_nivesout said:
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
Click to expand...
Click to collapse
1. I'm not the original owner
2. I'm not a Verizon subscriber. PagePlus Celluar [A verizon MVNO] is my service provider. They have much better plans, including monthly, and prepaid, if you ask me.
Kernel issue.
sent from my Sensation XD
Yess..
Good news! Got an email saying my phone has been shipped:
Code:
Original Problem:
TECHNICAL INQUIRY - PHONE FREEZING / LOCKED UP - FREEZE/DELAY BETWEEN MENU FUNCTIONS
Problem found:
BAD BGA COMPONENT
Solution:
REPLACED PBA
I guess the PBA is basically the motherboard? I suppose that could have been the cause of overnight freezing, and so my phone should be fixed.
Nice.. Just 2 days left on my warranty. Cutting it kinda close, I know lol
Very well done sir
sent from my Sensation XD
(summarized below in tl;dr version)
Since my problem I need help with showed up after going back to stock + root, I thought I'd ask in general before filling up the ROM discussion in development about the problem that I found after updating to ICS (leaked).
Had an odd problem crop up on me with scrosler's CleanROM 2.2 SP1 running (will 'splain in a sec, and tl;dr sum-up at the end), so I relocked, flashed back to pre-OTA official firmware and then let the OTA run. All was good, and I was happy. I unlocked again, installed Amon Ra, reinstalled SU, and started putting in my happy-fun root required tools (Oh Titanium, I likes you so). Then, my problem reappeared.
So my problem is occasionally the touchscreen would act "wacky" at times. Specifically, while in my browser, sometimes when I tried to scroll while browsing, the display would act like I was using pinch-zoom. It acted like I was touching the top left corner of the display in portrait mode, and zoom-in/-out according to how I was moving my touch that I intended to scroll. Then I noticed that games which required multi-touch had significant problems reading constant touch on most of the top-half of the display (left half in landscape mode with the carrier name on the left). I like Age of Zombies, and while the game would start off running right, within 20-60 seconds, the movement virtual controller would rapidly turn on and off, leaving me able to fire but not move. Grand Theft Auto was unplayable, as every time I touched a direction key in driving mode, the system would lose track of my holding the gas.
Troubleshooting took a while, as I had installed a lot of apps, and made a few changes at once after everything appeared to run properly. Ultimately, the problem appears to be caused by underclocking, and I can't figure out how to kill that and lock myself at stock speed. Haven't tried an overclocking capable kernel to see if they run any better, and haven't tried checking voltages to see if bumping them on underclocks would fix it.
I have used Antutu CPU master, an old version of SetCPU, and System Tuner Pro (from 3c). I can set the min and max CPU to 1.52, and it seems to stay for a while, but eventually, the setting reverts to allowing underclocking and my touchscreen gets goofy.
tl;dr: My system, even after restoring to RUU/OTA, wants to underclock. When the CPU runs under stock speed, my touch-screen misbehaves, particularly in gaming, but also in browsing. Any help?
Thanks
Can almost definitely confirm it's just bad hardware at this point.
After running 2 days without problem other than the touch-screen issue noted above, the phone entered an persistent bootloop after I loaded Juice Defender today. Phone would reboot, come up to home screen, get a data connection, tell me how many new email and texts I had, then tell me an app (same every reboot) was not responding and reboot 2-3 seconds after I cleared the error. Even when I managed to get to market before a reboot and uninstall the last 2 apps I'd installed, the phone is still in a boot loop.
Appreciate all that took the time to read, and wanted to share that there's a pretty good reason no one could respond with a solution.
Well, it probably is bad hardware but two cardinal rules I have when working on any Rezound is NEVER restore with Titanium BU & don't use Juice Defender (and I have a paid version of it).
I have had both mess up certain phones & I do this stuff all day at work.
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
AtLemacks said:
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
Click to expand...
Click to collapse
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Me 2
aostl said:
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Okay so I have a similar problem.
I have hephappy cm9 prefinal installed just started having problems with rom. screen was acting funny so I turned on the touch point developer tool supplied with the rom. I have found that I have multiple touch points when scrolling with one finger.
So I used a apk called touch recalibrate that I got when I was on mik's cm7.
Which I have recalibrated aprox 7 times with no improvements so I set my cpu to min 600 max 600 smartassv2 this did not help either. If anyone has the answer to this problem please let me know.