Related
If I use my Atrix for more than a few minutes it gets warm, which is not an uncommon thing. Any time this happens and I turn the screen off it will almost always crash. While the phone is cool it crashes randomly. This has happened on the newest releases of CM7, AT(Honeycomb)Rix, and The Dark Side. I have tried multiple clock speeds, and just setting the CPU at 1ghz no modification at all.
My last Atrix had Gingerblur on it and never crashed at all, I hardbricked it when I was trying to unlock it (dumb mistake). I went out got this phone, put these roms on it and ever since the very first day with these new roms any time the screen is off its very unstable.
----Never crashes while the screen is on----
Can anyone offer me any advice on the matter? Thank you in advance.
Wipe and wipe again, then try a stock rom, if it persists it's probably hardware related and you should bring it to the nearest motorola service centre.
Sent from my GT-I9100 using xda premium
Wipe everything using fastboot per multiple posts in the CM7 beta release thread before flashing CM7.
<edit> Found one for you. Wipe per the following:
http://forum.xda-developers.com/showpost.php?p=17466399&postcount=70
I installed cyanogenmod 7 on my Legend a few weeks back. It was running ok, today I thought about overclocking it. I had overcloced it before to 745 (or something) and it had worked fine so I thought about overclocking it to 850 (or something). As soon as I did that, it hanged for a while and then restarted.
Now everytime I start it, it restarts before I can do anything. All i managed was to enter the performance settings menu, but I cannot reach far enough to reset the CPU settings (it restarts)
Is there any other way I can reset the values, some file or something. I really don't want to reinstall everything.
What program are you using to over clock. Funnily this happened to me when I attempted to Oc (using setcpu) my legend to 864. However I installed the setcpu widget and I was able to change the speed asap. Maybe if you pressed fast enough then you might be able to restart before it restarts. But if all Is lost then factory reset is the way to go.
Sent from my Legend using xda premium
I was using the cyanogenmod 7 performance settings (settings>cyanogenmod>performance>cpu settings).
But I managed to reset it. I took out the memory card in hope that it will give me more time to reach the settings, and when I opened the CPU settings it was set to 600 MHz. looks like the settings were stored in memory card.
Hm
For future reference, don't check "restore on boot" until you know it's stable
Hi
In my case, overclocking is possible up to 844mhz, but I have reboot after few minutes. Max stable value is 806mhz (for me).
Maximal frequency depends of phone, every Legend are different. For one max is 768, for other maybe it 864.
Greetings
Sorry for my language
gosh... reading this post brings memory the last time i was messing with the performance thingy.... have to wipe my legend to get rid of the OC setting was my fastest option... but lost my unbackup data.
well you can try flashing your rom without wipe and hope things got back to normal.
on oc testing
my advice is this.... do your nandroid backup before doing OC testing...
if you have setcpu for OC testing... dont use the main bar to test oc...
but you can have setCPU to OC if certain condition like charging the phone is meet.
then if your system gone nuts just unplug the usb (not charging) and it will go back to main setting.
if you are using cyanogenmod performance setting.... do as TGF say.. do not set on reboot before you are sure that the system is stable...
plus you better nandroid backup first before messing with your phone...
My phone runs stable at 787............and I'm quite satisfied about the performance. But only because I have the power to, I'm thinkin about trying higher frequensies. Should I? Or it is an unnecessary risk?
Also, is there any preffered way to "try out" the performance once you set a new Max MHz?
I just installed CM9 beta1 and I'm having troubles with the overclocking. I tried the 768MHz but it freezes after a few seconds. Is there a way to overclock to a specific speed? I saw a while ago some guy saying that at aroung 728MHz it does a great job. I have kernel 2.6.35.13-htc-msm7x27-ics.
I got a bug, don't know if it's related to the ROM or the overclocking but when I set the minimum speed to 19MHZ, like on stock Legend, when I tried to wake my phone, it seemed to be stocked at 19MHz, so I couldn't do anything, had to take battery out. Happened to anyone else? It happened to me once since yesterday.
overclocking
I'm sure most of you probably know this but just in case..... If you get a program that allows you to see your logcat (google them) and clean the log of errors by removing problem apps or limiting their permissions. The result is you end up with a much more stable OS and you can then overclock a lot more heavy handed. With the changes, I very rarely have any problems and run at 864mhz. Hope it helps
Whip Jay said:
I just installed CM9 beta1 and I'm having troubles with the overclocking. I tried the 768MHz but it freezes after a few seconds. Is there a way to overclock to a specific speed? I saw a while ago some guy saying that at aroung 728MHz it does a great job. I have kernel 2.6.35.13-htc-msm7x27-ics.
I got a bug, don't know if it's related to the ROM or the overclocking but when I set the minimum speed to 19MHZ, like on stock Legend, when I tried to wake my phone, it seemed to be stocked at 19MHz, so I couldn't do anything, had to take battery out. Happened to anyone else? It happened to me once since yesterday.
Click to expand...
Click to collapse
What governor are you using? If your using power save or conservative that will defenitly cause it.
Sent from my Legend using XDA
I could never overclock my Legend. Always near-instant reboots . Consider yourself lucky if you can!
(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.
Please go easy on me, here. I know how to search forums, I just don't always understand what I read on here. :laugh: My husband has always helped me with most of my Vibrant issues, but he has recently defected to his HTC One S.
My Vibrant is getting unbearably slow. I'd been running a Fishman rom on it, and it seemed very, very slow. We then decided on the Slim Ryder rom. The first day or so it was unbelievably fast. That, unfortunately didn't last.
I have only the minimum apps on there and only one updating widget (BeWeather time and weather. Used to use Beautiful Widgets but it began superimposing the time over itself so I couldn't read the time...).
I'm a realist, and I know that my Vibrant is old. I know it isn't as fast as The Hubs' new HTC. I'm only comparing it to itself. Here's where I've noticed the slow downs:
*when switching portrait/landscape (sometimes tries to show half a landscape screen in portrait mode)
*when touching a text field, it is very slow to bring up the keyboard...sometimes i have to tap multiple times
*when Swyping or using Swiftkey, it sometimes hangs on a letter
*it takes several seconds to bring up my text messages, dialer, call logs...basic phone functions.
*using the browser is unbearable.
I've done the old standard...Master Reset, cleared history, caches, cookies, etc. I have wiped call logs and clear out my texts every other day. I don't store music on my phone (Google Music) and have my photos upload to my Google+ account via wifi so I don't get a lot of that stored up. I do not use a live wallpaper.
I'm not eligible for an upgrade until November. I am absolutely open to trying other ROMs, but as a mama with little people and no landline, having the ability to reach 911 from my phone is non-negotiable. Can anyone offer me any ideas on how to limp through until my upgrade?
Thanks in advance.
My vibrant was pretty slow with 2.1~2.2 using almost any rom;gingerbread was a huge improvement and ice cream sandwich is just blazing fast. I would suggest flashing ICS passion http://forum.xda-developers.com/showthread.php?t=1362961 or another rom that supports 911. Right now, the developers are working on porting jelly bean to our phone, and when its stable, go grab it!
2.1 and 2.2 roms I heard are a lil slow so try to use an ics rom like passion chimera or zenwick
Sent from my SGH-T959 using xda app-developers app
You can check out the kernel bible thread and maybe get a kernel with voodoo lagfix, seems to make my phone faster. I'm running 2.2 Blue Frankenstein ROM, it comes with voodoo lagfix.
Sent from my SGH-T959 using xda premium
Try a kernel with voodoo lag-fix as iTz KeeFy mentioned and in the meantime disable any animations.
tc
The_MamaBee said:
My Vibrant is getting unbearably slow. I'd been running a Fishman rom on it, and it seemed very, very slow. We then decided on the Slim Ryder rom. The first day or so it was unbelievably fast. That, unfortunately didn't last.
<snip>
*when switching portrait/landscape (sometimes tries to show half a landscape screen in portrait mode)
*when touching a text field, it is very slow to bring up the keyboard...sometimes i have to tap multiple times
*when Swyping or using Swiftkey, it sometimes hangs on a letter
*it takes several seconds to bring up my text messages, dialer, call logs...basic phone functions.
*using the browser is unbearable.
Click to expand...
Click to collapse
Fellas, if she is using Slim_Ryder, then she is using a kernel that already has Voodoo included, IIRC.
To me, these symptoms sound like you may be getting bogged down on your low-end CPU frequencies. Maybe get something like SetCPU or CPUmaster from the market and up your lowest frequency to the next step. When I am on a 2.2 ROM, I use BaliX1.2 and I have mine overclocked to 1.2ghz but my lowest frequency is 400ghz and not the standard 100-200 that most use. I find that this bogs my system down a bit more than it should. So that is when I decided to test it out and up the lowest in step increments.
You can go to my Battery Guide and in the 3rd post, there is a link to get SetCPU for XDA users for Free. When you use this, you might also want to check the governors as well. Some 2.2 kernels do not play well with On-Demand (BaliX most definitley does not-proven a long time ago). I have mine set to conservative and no profiles set at all. My I/O is Deadline also.
Woodrube said:
Fellas, if she is using Slim_Ryder, then she is using a kernel that already has Voodoo included, IIRC.
To me, these symptoms sound like you may be getting bogged down on your low-end CPU frequencies. Maybe get something like SetCPU or CPUmaster from the market and up your lowest frequency to the next step. When I am on a 2.2 ROM, I use BaliX1.2 and I have mine overclocked to 1.2ghz but my lowest frequency is 400ghz and not the standard 100-200 that most use. I find that this bogs my system down a bit more than it should. So that is when I decided to test it out and up the lowest in step increments.
You can go to my Battery Guide and in the 3rd post, there is a link to get SetCPU for XDA users for Free. When you use this, you might also want to check the governors as well. Some 2.2 kernels do not play well with On-Demand (BaliX most definitley does not-proven a long time ago). I have mine set to conservative and no profiles set at all. My I/O is Deadline also.
Click to expand...
Click to collapse
Thank you very much. It was the Blue Frankenstein 2.2 ROM I switched from to go with Slim_Ryder. Both have been very laggy.
I will definitely try the steps you've outlined for me, Woodrube. I really appreciate it. I know I'm using a Bali Kernel. It says Bali v1.8.8UV.
I spoke with a second-level tech at Tmo this morning and he said I've done all the troubleshooting steps they could recommend. He said at this point it is a hardware issue.
I will try these steps today and research how I can test my 911 capabilities legally. If if can get over those obstacles, I will definitely try an ICS Rom. I just have to limp through until early November.
Thanks again for the help, guys!
Hello all.
As the title says, I've been having random reboot sessions on my phone lately. When these reboot sessions occur, the battery gets hot.
I'd like to give some more information about my situation:
I've been using CM7.2 on my Huawei u8160 for almost half a year now, without any kind of problems. Lately, the phone started rebooting randomly, especially during phone calls, making the phone almost useless. The reboots also occur when the phone is idle. These reboots drain the battery extremely fast.
I've been using CM7 with the V6 supercharger, as I said, for months without problem. When these reboots started happening, I reflashed the rom, doing a full wipe (clear cache, clear dalvik, format system, format data, factory reset etc.) , but that didn't solve the problem. I reflashed CM7 several times, with / without V6 supercharger, without deleting those system apps that are safe to remove (live wallpapers, update notify etc.). I also reflashed the stock froyo rom the device came with. None of these methods worked.
It is getting more and more frustrating, since they occur randomly, and I can't make a proper phone call, since it's almost guaranteed the phone will reboot during the conversation.
I tried formatting the SD card, using another SD card, resetting the battery stats, using a program on the market and the CMW Recovery - nothing helped.
Another thing I noticed (this may sound very stupid) is that the phone reboots more often when I'm outside (it's winter here now), or when I enter in a warmer place, or when the phone is in my pocket.
I asked an assistant from a nearby Vodafone store, she said that it is a software problem ( -.- ) and that the phone needs to be sent for service. I told her I've already reflashed the software, and she said I only did an update not a full soft flash (lol).
I would really appreciate if anyone could give some suggestions, or help me in any way.
I have also created an error report using the device specific setting menu included in the CM7 rom, which I am attaching here.
Help is greatly appreciated. Thank you in advance.
pneuma00 said:
Hello all.
As the title says, I've been having random reboot sessions on my phone lately. When these reboot sessions occur, the battery gets hot.
I'd like to give some more information about my situation:
I've been using CM7.2 on my Huawei u8160 for almost half a year now, without any kind of problems. Lately, the phone started rebooting randomly, especially during phone calls, making the phone almost useless. The reboots also occur when the phone is idle. These reboots drain the battery extremely fast.
I've been using CM7 with the V6 supercharger, as I said, for months without problem. When these reboots started happening, I reflashed the rom, doing a full wipe (clear cache, clear dalvik, format system, format data, factory reset etc.) , but that didn't solve the problem. I reflashed CM7 several times, with / without V6 supercharger, without deleting those system apps that are safe to remove (live wallpapers, update notify etc.). I also reflashed the stock froyo rom the device came with. None of these methods worked.
It is getting more and more frustrating, since they occur randomly, and I can't make a proper phone call, since it's almost guaranteed the phone will reboot during the conversation.
I tried formatting the SD card, using another SD card, resetting the battery stats, using a program on the market and the CMW Recovery - nothing helped.
Another thing I noticed (this may sound very stupid) is that the phone reboots more often when I'm outside (it's winter here now), or when I enter in a warmer place, or when the phone is in my pocket.
I asked an assistant from a nearby Vodafone store, she said that it is a software problem ( -.- ) and that the phone needs to be sent for service. I told her I've already reflashed the software, and she said I only did an update not a full soft flash (lol).
I would really appreciate if anyone could give some suggestions, or help me in any way.
I have also created an error report using the device specific setting menu included in the CM7 rom, which I am attaching here.
Help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Yeah, going to the store after flashing a custom ROM is rarely going to yield favorable results. Honestly, I'd try clearing app data and fixing permissions. What recovery are you using? When in doubt, wipe twice.
Jimmy_Christ said:
Yeah, going to the store after flashing a custom ROM is rarely going to yield favorable results. Honestly, I'd try clearing app data and fixing permissions. What recovery are you using? When in doubt, wipe twice.
Click to expand...
Click to collapse
Yeah, I know that rooting void varranty and everything but the naive me thought maybe they can say something clever...
I tried clearing everything, formatting system, data, cache, everything, fixing permissions etc.
I'm using ClockworkMod Recovery 5.0.x.
I am planning to buy a new battery because I observed it's getting really hot sometimes, and after the reboots occur, it's also really hot.
pneuma00 said:
Yeah, I know that rooting void varranty and everything but the naive me thought maybe they can say something clever...
I tried clearing everything, formatting system, data, cache, everything, fixing permissions etc.
I'm using ClockworkMod Recovery 5.0.x.
I am planning to buy a new battery because I observed it's getting really hot sometimes, and after the reboots occur, it's also really hot.
Click to expand...
Click to collapse
The more time you devote to this the more you'll realize that most of the folks at the stores dont know much. It wont hurt to buy a new battery. Wipe the battery stats. Do you use a custom kernel? Ovetclocked? Underclocked? Played with the voltage tables?
Sent from my SPH-L710 using xda app-developers app
Jimmy_Christ said:
The more time you devote to this the more you'll realize that most of the folks at the stores dont know much. It wont hurt to buy a new battery. Wipe the battery stats. Do you use a custom kernel? Ovetclocked? Underclocked? Played with the voltage tables?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, you're right...
I did wipe the battery stats, let it drain completely and did a full recharge. For the kernel, I don't really know much about these stuff (yet). This is the ROM I use : http://forum.xda-developers.com/showthread.php?t=1259739. Im my phone info menu it says 2.6.32.9-perf [email protected] #23 (no idea what this means) so I don't know if it's a custom kernel or a stock one. For clock values I use min: 30MHz max: 600MHz (which is the stock value if I'm not wrong). I don't know what you mean by voltage tables, I'd appreciate if you could explain that.
Thanks so far.
Well basically in a nutshell, voltage is the power sent to the CPU. Some custom kernels allow for what's called undervolting. Basically you're you're lowering the amount of power sent to the CPU, where in theory you'll achieve better battery life. However, this can be very dicey. I would not recommend playing with voltage tables until you're a bit more experienced. I asked because undervolting can lead to boot loops and seemingly random reboots. You're running a solid rom with cm7. If you didn't touch it, then that's the stock cm rom. Have you searched the forum thread?
Sent from my SPH-L710 using xda app-developers app
Jimmy_Christ said:
Well basically in a nutshell, voltage is the power sent to the CPU. Some custom kernels allow for what's called undervolting. Basically you're you're lowering the amount of power sent to the CPU, where in theory you'll achieve better battery life. However, this can be very dicey. I would not recommend playing with voltage tables until you're a bit more experienced. I asked because undervolting can lead to boot loops and seemingly random reboots. You're running a solid rom with cm7. If you didn't touch it, then that's the stock cm rom. Have you searched the forum thread?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yes, I haven't touched anything in the ROM I'm using currently.
I've been searching the forums for days before starting this thread, without success.
What I noticed about the reboots is that it occurs almost exclusively when making / receiving a phone call and when the phone is idle.
*edit: I forgot to mention that I'm using Segoe font, not sure if that makes a difference though. I have replaced almost every font in the /system/fonts folder (droid sans+bold+mono and even droid serif+bold+italic+bolditalic)*