Related
So I've had less than stellar luck with this phone. I purchased it and rooted it pretty much on day 1, (this was back in early May) and immediately started seeing some pretty awful rebooting. I switched kernels from Das Bamf's to Imoseyon's, which helped it go from mind-numbing to merely bad (used to reboot EVERY TIME the screen was slept and turned back on, went to happening maybe once an hour)
I switched back to stock, same problem, rebooting literally once an hour. I called Verizon for troubleshooting help and they immediately had me switch it out for a Hardware version 2.0 phone, which I've now had since May 15th. It does work a lot better, but it's still pretty bad. Here's the timeline:
Ran stock for about a week, was seeing 1 reboot every other day, decided to root. Installed BAMF remix 1.7 with the .7/.6 CDMA/LTE radio, which left it pretty much the same, rebooting every 30 hours or so. It's particularly likely to do it when using Navigation or on phone calls. It's not a stress thing, I can run Linpack, quadrant, make calls and surf, whatever, it runs fine at stock speeds, 1.92, 1.92x... and will do so for hours without rebooting (until it does)
Switched to 2.0 w/ the MR2 radio, and the reboots were even worse. Now more like 1-2 times a day. Thinking this was not a radio issue now, I eased down the clock speed (I was running 1.92x kernel) down to stock speeds, no affect. Upped the voltage by switching to 1.92, still no affect, reboots a couple of times day, ALSO with a few random shutdowns thrown in for fun. I tried Standard as well, letting it top out at 1.4, still having the issue.
MR2.5 came out, switched to that, and it became unuseable. Reboots literally every 5-10 minutes, and I tried running it that way for the better part of a day, thinking it was maybe the kernel settling or whatever, but it stayed that bad. I switched back to 2.0 and kept seeing the reboots a couple of times a day, so since they were worse on GB I figured I'd go back to Froyo.
Loaded 1.8 Remix, and the reboots are still happening a few times day. At my wit's end, I decided to go straight back to stock, no root. It ran fine that way for about a day, then randomly shutdown again. It has seemed good so far today, but the random shutdown happening makes me assume it's still not stable.
I really don't think it's a problem with 2 phones in a row, and there's thousands of posts of people experiencing similar problems, so it's not something weird I'm particularly doing. There seems to be no rhyme or reason to it, as some people are rock solid with Froyo with the .7 radios, or the .6/.7 combo, or some are fine with Gingerbread MR2, or even 2.5. Me, I have no luck with ANYTHING.
Should I start another ticket with Verizon for another dud phone, or is the promised OTA update really going to do something magical that MR 2 or 2.5 haven't already tried to do to fix this thing?
If it were me Id be screaming at somebody at Verizon. If your sure that nothing u did rooting or flashing roms caused the reboots then get a new phone. Rumors say that gingerbread is coming tomorrow but you can't out to much stock in that and even if it does I doubt there is any miracle code written in that's gonna help you.
Sent from my ADR6400L using XDA App
Some people have had random reboots on stock rom. But since you were on stock for less than a day, it's impossible to determine whether the reboots are due to a defective phone or something that happened during/after you flashed the custom rom. You obviously know your way around various roms, radios & kernel/cpu tweaks, and nothing seems to help. If you have the patience, go to the IRC channel for more suggestions. If no one there can help, I would restore to stock & exchange the phone. You may have a defective device that will never work right.
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
The devs would say do a full format and flash and see if it still happens.
Sent from my LG-P500 using XDA App
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Try tuning down your overclock frequency... if you have overclocked it... it sometimes happens cuz of that... if you havent overclocked then theres some other problem...
Sent from my LG-P500 using xda premium
samrox144 said:
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Click to expand...
Click to collapse
I've done that, but does logcat hold on to recent logs automatically, or do I have to turn on "save to sd card"?
I think I might be having this same issue. I left my phone on and plugged in to charge not even for a half hour or less then I came back to it later and pressed the power button to try to turn it back on but it wouldn't turn on. Then I pressed and held it a second and it wouldn't turn on. I unplugged the battery then plugged it back in then it powered up fine. I seem to be having this issue every once in awhile and I am not quite certain why it is doing this. Also it seems like it has an issue with charging on my computer. I plug it and it the computer is telling me that it can be connected to a higher speed port which makes no since as I have 2 usb 2.0 ports and 1 usb sata port. But basically I plug it in with a full charge and it has no problem keeping it charged but when it ends up going down to at least 50% the charge just keep deceasing and never charges. I just hope that I can make it stop this as it is getting quite annoying maybe it is just the battery or something but I can't see how as it isn't even 6 months old.
I've tried using Logcat but unless you set it to save the log every few seconds it doesn't help. If there's an error it doesn't get caught by Logcat because whatever it does, it turns off the whole phone.
What are you overclocked to?
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Oneiros42 said:
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Click to expand...
Click to collapse
Well then. I don't know. Have you tried reflashing the ROM?
Not yet. I was hoping Mik's CM7 6.6.1 would have been declared stable by now, but I guess I'll have to settle for 6.5.8.
Quick off-topic question: ADW Launcher always comes to a grinding halt immediately after a reboot, to the point it gives the force-close option window. Is that because there are widgets installed to the partition on the sdcard, thanks to app2sd? I checked under applications and it says they're installed to the phone, but I thought I heard that app2sd (I'm using Darktremor's, as suggested by Mik) effectively takes the option out of your hands, making it moot. If that's the case, how do I delete the partition, since I'll be doing a full wipe and reinstall when I flash the ROM again.
I don't play games 2
Dammit! Yesterday I did a complete wipe (return to factory, wipe dalvik), reformatted the sd card, and updated the ROM to 6.5.8 and it just shut down on its own again. I even saw it happen... while it was sleeping, I saw the buttons light up and blink once or twice, then it shut off. The screen stayed off.
I did a clean install and haven't touched the clock settings. I reinstalled my apps of course, but I don't have anything that runs constantly in the background that I'm aware of. I installed ADW Launcher EX, I don't know if that matters.
Does this mean it could have a physical fault somewhere? I'd really hate to have to go through the hassle of reloading the LG stock ROM and unrooting it (that's possible, right) to send it in for repair.
I had the same problem with gingerbread and the related roms.
But my problems were about the overclock frequencies. I used the italian rom GingerLoL 1.5.2 and I set the frequencies in this mode: 320-729 smartass v2. No more problems.
I don't know why I hadn't this problem with Froyo's rom...
I'm tempted to fiddle with the clock settings now that I know just reflashing the rom doesn't help. It seems by default CM7 is set to 245-600mhz, with the "smartass" governor. I figure I might as well bump the low end to 320, but where's the "v2" version of smartass you mention? It's not in the list.
I have exactly the same issue! Tried 3 different firmwares, 3 different roms and different kernels too, but it seems to reboot by itself and also really slow sometimes to scroll. Can't solve this... maybe some hardware troubles? some new defected cpu ? I sent this phone 1 month ago in warranty and they changed me the logic board, then when i got it back, it started to have this trouble. Before this, never had this trouble.
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
FPChaim said:
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
Click to expand...
Click to collapse
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Oneiros42 said:
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Click to expand...
Click to collapse
I'm my case the phone boots and when it load all the aplications it reboots... but one time i quickly go to setting>applications>manage applications and there has less than 1 mb... so i think it was building something like caches... I wiped everything and my phone worked as usually... but i installed a lot of things again and it keeps rebooting and rebooting... i wiped everything again and installed just few things, leaving my phone to have high internal memory... it worked!(actually i have 42 mbs of free space and it never happened again)
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
I admit there are some issues with the battery and heat and bugs, but i have not experienced any freezing with the stock browser or any program really, alarm clock extreme and it works for me, I don't use the Facebook app often but the few times i have, no real issues sometimes it lags trying to update. I will say thay the market SUCKS or play whatever they call it. Maybe you got a corrupt OTA file or something is wrong with your update installation. Maybe try doing a factory reset, i know that sucks to do but i do it before every OTA and im not really experiencing any of the software issues you are experiencing. If that doesn't help, root it and use the razr 1.7 utility to reinstall the system files.
Did you try to wipe the device (factory default)? It helped in my case.
Sent from my XT910
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
abw1987 said:
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
Click to expand...
Click to collapse
Data wipe, itll fix it. If you dont want to.do.that then root and wipe the cache and dalvik cache.
Sent from my DROID RAZR using Tapatalk 2
AndroidGreg said:
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
Click to expand...
Click to collapse
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
syrnett said:
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
+1
ICS is very different from GB, and Motonverizola tried really hard to get ICS to play well with existing GB cache data and GB settings. All of that stuff changed a LOT.
The problem isn't ICS: the problem is data conversion from GB to ICS.
Wipe the cache and dalvik. If that doesn't get it, then do a factory reset and set everything up again.
Mine runs for days with light use (1-3 hours a day), or a day+ with heavy use. It doesn't get hot, unless you mean that the other way. But that'd be kinda creepy.
Hi
This is my first post here at this forum and I'm not a Razr user but thinking about getting the Maxx because of it's hardware and big battery which fits my usage of a smartphone, I have a Galaxy S right now.
I have looked at some of the posts and screenshots of the battery usage on the new leaked/released ICS for the Razr and read about complains about the short lived battery and the devices that overheat, well, we had the same problem when GB has been released to the Galaxy S and that is all related to the Android OS app that is using the battery because it's got into a loop, this will not get fixed unless you make Motorola aware of the problem. I could be wrong but I think that is related to the dalvik-machine. Android OS should be using around a single-digit of the battery of all time (3%-7%), we don't have this issue anymore since Samsung fixed this bug in the later releases of GB firmwares.
A temporary fix of the Android OS is to reboot the phone when you can see that it's hijacking the battery, this is until Motorola fixes the issue.
I wish you all good luck and hope that you will get a better firmware soon.
Its always good practice to start fresh when accepting an update that big. Less variables = less problems.....
Id do a factory reset and start from scratch... that sux... i know, but so does a useless phone
Ics def wasnt all the hype.... but its also not that bad... just gotta start clean.
Good luck!
Complete disaster? How is it a disaster compared to my update? After the update I could no longer receive text messages, Consider the fact that I send a receive hundreds of text messages per day this is honestly the biggest cause of outrage I have with a flagship that can't perform even what a Nokia 6280 could, when I finally receive texts they come in 4 hours late and worse still, in DUPLICATES and I can't seem to find any solution to this as of yet. A factory reset fixes this for an hour at best but the problem suffices after that. Does anyone have a SOLUTION to this? Honestly driving me nuts
I agree with most others... do a factory reset. I always do after a major upgrade (and ICS is a major upgrade!)
Then check what apps you are putting on the machine; some cause issues. For instance, I put the new Starbucks 2.0 app upgrade on my phone yesterday - consumed battery like mad, phone ran hot (like cook-an-egg-on-it hot), runaway processes, etc. Turns out it was the new Starbucks app; after removing it the phone ran normal.
Otherwise I love ICS! So try the cache wipe; and if that doesn't help then do a factory reset and reinstall things. Takes time, but it saves in the long run.
Wow, this is crazy to hear. My update has been flawless but I did a factory reset after getting it. I bet if you did that it would fix 99% of your problems.
I also rooted after and now I'm running a cm9 rom. This is the best my phone has ever run.
Ultimately, even if you don't root you can fix most of these problems with a factory reset.
Sent from my Droid Razr using xda premium
Hold down the Home button to see what's running, download a task manager to see what's dominating the CPU. The phone won't get hot by itself, something is using up the CPU (like you said) if you don't want to factory reset you've got to figure out what it is. Rooting and setting the CPU governor to hotplug will save quite a bit in battery (shuts the 2nd core off when not needed).
I'm on a Canadian leak, the first day battery performance was terrible. By the 4th day, the battery lasted longer than GB
I concur with everyone here about the factory reset.
As other's have mentioned, going from GB to ICS is a major overhaul. I've read elsewhere what this really entails and it's not pretty. Suffice it to say, I backed up all my user apps and data (using Titanium Backup), saved off all other things that were on my internal SD card just to be safe and then applied the OTA update in stock recovery, wiped data and cache and rebooted. I then rooted, installed Safestrap and flashed Eclipse ICS v1.2 RC1 and restored my apps with TiBu.
I also tried stock ROM as well and restored my apps via TiBu.
In both cases, no performance issues nor forced closes. Runs like a champ.
I'm running the latest .214 leak and my battery life has improved over .211.
.214
Razr Maxx
I was having shorter battery life with the ICS .211 build and then updated to .214
My battery life is way better then it ever was with GB or ICS .211
I ran it the other day for 36hrs and 3 of it actually talking on the phone and had 20% battery life left.
It has currently been on for 4hrs 6 min and is at 90%. light email and phone use. I do have an IMAP email account that poles every 10 minutes with push for instant updates.
Mine is running fine after simple reboot
I am getting great battery life and my Razr Maxx is working almost flawlessly after the ICS OTA stock update. I just rebooted it shortly after the update when it was running hot and haven't had any problems since.
If .214 is even better, great.
Looking forward to Jelly Bean to get even more from my device.
Jeff
Was on the soak test and had the same battery problems. Only way to fix was via a factory reset. This did however fix all the problems.
Cant use motocast, it wont connect to my motocast on my mac. So i cant sync my media. How to solve this?
Sent from my XT910 using Tapatalk 2
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
abw1987 said:
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
Click to expand...
Click to collapse
Its under the advanced menu.
Sent from my DROID RAZR using Tapatalk 2
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)*
Hey guys,
I have been running Entropy512's US kernel on my stock, rooted XXKPL YP-G70 for a while now. I have been suffering from random 1-2 second freezes, and capacitive buttons go dark, every once in a while. I noticed others also seem to have experienced it as well from the posts in the kernel's thread (Can't post there yet as I have not gotten 10 posts). I tried changing scheduler to noop, which does lessen the frequency of occurrence of the freezes but they are still there. I am using ext4, checked with mount in adb shell, so I don't think it is rfs lag. The freezes are usually random, but I can reproduce them somewhat consistently by repeatedly scrolling through a list or something (like songs in the music player, or a website, etc.) very fast. Got it to freeze about 4 times within 5 minutes. I tried to see if something showed up in logcat and I saw that every time this freeze happened, it showed:
W/PowerManagerService< 132>: Timer 0x7->0x3:0x0
in the logcat. What is that? It shows up without fail every time I get the freeze. Did anybody ever have any luck with figuring out what is going on? I suppose I can live with it, but it gets a bit annoying sometimes.
Thanks
divergens said:
Hey guys,
I have been running Entropy512's US kernel on my stock, rooted XXKPL YP-G70 for a while now. I have been suffering from random 1-2 second freezes, and capacitive buttons go dark, every once in a while. I noticed others also seem to have experienced it as well from the posts in the kernel's thread (Can't post there yet as I have not gotten 10 posts). I tried changing scheduler to noop, which does lessen the frequency of occurrence of the freezes but they are still there. I am using ext4, checked with mount in adb shell, so I don't think it is rfs lag. The freezes are usually random, but I can reproduce them somewhat consistently by repeatedly scrolling through a list or something (like songs in the music player, or a website, etc.) very fast. Got it to freeze about 4 times within 5 minutes. I tried to see if something showed up in logcat and I saw that every time this freeze happened, it showed:
W/PowerManagerService< 132>: Timer 0x7->0x3:0x0
in the logcat. What is that? It shows up without fail every time I get the freeze. Did anybody ever have any luck with figuring out what is going on? I suppose I can live with it, but it gets a bit annoying sometimes.
Thanks
Click to expand...
Click to collapse
I've never experienced anything like that with EDD. However, it's been a long time since I've used it. I don't recommend posting in that thread. It's an old thread and Entropy512 does not support it anymore. If it were me, I'd wipe everything and start fresh. I bet you don't get any "freezing" on a fresh install. It's most likely an app, combination of apps or too many running apps... Just some thoughts though... Hope it helps.:laugh:
Thanks for the reply Meticulus.
Yeah, I have tried completely wiping my player and starting from stock with Entropy512's kernel. Tried with the original 2.3.5 US firmware, XXKPH, XXKPL, and still get the same freezing. Only happens with his kernel as well. Oh well, I think I am just gonna go back to stock. When I get more time, I think I am gonna try SlimKat, it looks pretty functional and now that the camera is somewhat working (nice job on that by the way:good, I could see myself using it daily . Gingerbread is pretty hard to use now that I have gotten used to using my Nexus 7 and Moto G :laugh:.