Related
So my just powers off, doesn't matter what state the battery in. It does not reboot. It just turns off. I have no idea what is causing this and I have been running this setup for awhile now without problems.
ROM: BAMF Stripped 1.7
Kernel: leanKernel 1.92x
Any ideas?
engagedtosmile said:
So my just powers off, doesn't matter what state the battery in. It does not reboot. It just turns off. I have no idea what is causing this and I have been running this setup for awhile now without problems.
ROM: BAMF Stripped 1.7
Kernel: leanKernel 1.92x
Any ideas?
Click to expand...
Click to collapse
You're burning up the CPU from overclocking it?
Asside from that obvious first, thought. I'm leaning more and more towards the fact that these sd cards are having issues wiping the info off of them. You know, the one that comes with the phone that's 32GB.
I've noticed that with mine I keep having issues seeing partitions and wiping old information off of the sdcard for that matter.
I won't delve to much in to details but I know for a fact that a couple of times that I've told my phone to wipe info from the sdcard, it leaves stuff behind and i tshows when I boot up in to my freshly installed ROM what ever it may be at the time.
I've even gone as far as booting in to gparted only to see that it doesn't see the partition...
thewebsiteisdown said:
You're burning up the CPU from overclocking it?
Asside from that obvious first, thought. I'm leaning more and more towards the fact that these sd cards are having issues wiping the info off of them. You know, the one that comes with the phone that's 32GB.
I've noticed that with mine I keep having issues seeing partitions and wiping old information off of the sdcard for that matter.
I won't delve to much in to details but I know for a fact that a couple of times that I've told my phone to wipe info from the sdcard, it leaves stuff behind and i tshows when I boot up in to my freshly installed ROM what ever it may be at the time.
I've even gone as far as booting in to gparted only to see that it doesn't see the partition...
Click to expand...
Click to collapse
I have caught it saying that the SD card was inaccessible but I don't see why that would make it power down. I lowered the overclock back down to 1.4ghz to see if it helps.
Just curious.. but are you running the "new" radio that came out with the OTA update? (Obviously not the official OTA, but the leaked version? and no I don't mean GB radio).
Hubby's phone started doing this after he got the OTA. I wasn't even rooted at the time but the new radio started causing his phone to shut down. Mine which was rooted and had received the leaked and rooted version of the OTA was rebooting at random times throughout the day.
This weekend I flashed them both back to the previous radio (Combo #2 in the obligatory radio post) and they've been running ever since with no shutdowns or reboots.
engagedtosmile said:
I have caught it saying that the SD card was inaccessible but I don't see why that would make it power down. I lowered the overclock back down to 1.4ghz to see if it helps.
Click to expand...
Click to collapse
I have mine set to 1.4. There's no reason besides for epenus to really go over that IMO. You don't want to burn the CPU up. Even at 1.4 you need to find out if it likes to be undervolted or uber undervolted as well. Mine was happy with uber undervolt then on the next couple kernels that came out that changed to the undervolted so..
That part is a crap shoot. The sd card is deffinately causing some funky behavior IMO. Probably not shutting down like you said but funky things none the less and I really wish I could get a better handle on it.
I had a program the other day on my computer that seen the partitions fine and now none of them do that I try. I don't know if I'm using the wrong app now or what...
I'm busy getting ready to move in to a house right now though so I'll get to it more later I suppose for now I'm chilling on GB.
I agree with Sam as well a little I suppose but Sam, factory resetting the phone is supposed to fix the new ota update issue or atleast it did for my wifes phone. That was per HTC's advice that we tried that with hers and hers is unrooted not even touched and it stopped it so..
Some people say it didn't work for them but that's neither here nor there..
thewebsiteisdown said:
I have mine set to 1.4. There's no reason besides for epenus to really go over that IMO. You don't want to burn the CPU up. Even at 1.4 you need to find out if it likes to be undervolted or uber undervolted as well. Mine was happy with uber undervolt then on the next couple kernels that came out that changed to the undervolted so..
Click to expand...
Click to collapse
I play a lot of PSX on my phone and the few FPS helps sometime. Also helps with the audio becoming choppy.
And yes, this is the leaked radio but I have been using it since day one. I lowered it to 1.4ghz and I think was it. The rise in temperature outside probably wasn't helping.
engagedtosmile said:
I play a lot of PSX on my phone and the few FPS helps sometime. Also helps with the audio becoming choppy.
And yes, this is the leaked radio but I have been using it since day one. I lowered it to 1.4ghz and I think was it. The rise in temperature outside probably wasn't helping.
Click to expand...
Click to collapse
Sweet glad I could help. You should thank me and Samxxx .
thewebsiteisdown said:
Sweet glad I could help. You should thank me and Samxxx .
Click to expand...
Click to collapse
It happened again last night so it wasn't the OC afterall, I am on the stock radio now.
Happened again with stock radio, I'm out of ideas as to what is causing it.
engagedtosmile said:
Happened again with stock radio, I'm out of ideas as to what is causing it.
Click to expand...
Click to collapse
Mine did this a couple times. I read some stats and realized it was reading the battery as dead when it would happen. So I took the battery out and made sure it was in firmly and correctly, made sure the battery door was on tight and it never happened again.
Is the phone actually powering off or is it just not waking up? If its not waking up then its just undervolted to much. I would try another kernel that's not as undervolted.
Sent from my ADR6400L using XDA Premium App
dlongb13 said:
Is the phone actually powering off or is it just not waking up? If its not waking up then its just undervolted to much. I would try another kernel that's not as undervolted.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Powers off completely.
I think I found the issue, it's the hardware. If I put any pressure on it or if it bends a little, it will power off like its shorting out. (Happens mostly in my pocket while sitting.) Going to talk to verizon about it.
Bad thing is you don't like to use the thank you button so I won't be helping you any more at this point.
thewebsiteisdown said:
Bad thing is you don't like to use the thank you button so I won't be helping you any more at this point.
Click to expand...
Click to collapse
lol okay.
heres your thanks.
Thanks.
My phone seems to be having a similar issue. I'm running BamfGingerRemix 2.1, the MR2 radio, with Nerozehl's Dream Kernel, overclocked to 1.4Ghz, and with swap enabled. The low clock speed is 368.
I have no idea what is causing it, but I'm pretty sure the phone is actually off. I have to do a battery pull before I can get it to boot. This has happened 3 times over the past 3 days. If it happens again, I'm going to call myself from my roommate's phone to see if it is truly off.
I know it isn't from the battery being too low because last night after I got it rebooted, the battery was at 99% (it was on the charger when I tried to wake it). I'm hoping this isn't a sign of something bad coming to my phone.
I've heard some people call this the sleep of death? I'm on aosp (both cm7 and OMFGB) and I've seen this a few times. Werid eh?
Edit: I'm on the 402w1 radio
Sent from my Thunderbolt using XDA Premium App
My phone would also not wake up a few times when I was running various BAMF Roms - I should note that I have only run their ROMs since rooting the phone. It seemed to happen a few minutes after sending a text, not every time but randomly. I haven't changed any of the defaults regarding overclocking, so it would seem strange if that was the reason. I also don't know if it was off, or if it just wouldn't wake up because I had to pull the battery to get it running again.
However, I have been running the newest 3.0 RC3 for a couple of days and haven't seen it happen at all.
So I just got my g2x, rooted,nv and cwm. Flashed cm7 and I keep getting s.o.d(screen of death). I thought was rom problem so I.changed rom and im on xdblasters 1.1.0 and keep on getting them. Any solution orhelp would be appreciated.
Sent from my LG-P999 using XDA App
Not sure I know of a rom for g2x called xdblasters.
Also, what kernal are you using? Are you overclocking or undervolting? Are you using setcpu or pimpmycpu? What is your max and min cpu settings? When you flashed, what was your procedure for wiping? Did you fix permissions after flashing? Did you use a program to restore apps? Did you use that program to restore system settings? Did you choose to restore apps and settings from google account?
The answers to all of these questions could help determine what you've got going on.
I apologize, its x boarders. And well I am using fauxs newest kernel currently using 1.1 overclock but it would also happen while at stock cpu with previous rom.i don't restore with google but I use titanium backup for batch. When I do new roms I always follow the clean slate rule;Wipe data,cache,dalvik,bat stats. occasionally I forget fixing permissions but I do when I get alot of force closes.
Sent from my LG-P999 using XDA App
I didnt' see you mention formatting /system under mounts and storage. This is a critical step.
If it were me, I would try to keep everything as basic as I could each step of the way so that i could try to pinpoint the issue. Start by wiping everything (including sd card...just backup your user added stuff to your pc) and install a stock rom/kernal. See if it occurs stock...who knows? It's possible your phone is bad. Then if it doesn't misbehave with stock, then I would wipe everything again, including sd cards (interal and external), and flash cm7 (keeping cm7 kernal). I would try manually installing apps again, rather than using titanium backup or google restore. Just hook up to wi-fi (so you don't waste your data mileage) and go to market/myapps and redownload (hopefully you have a list of what you have).
But something to point out. On my phone, when I use CM7 (with stock kernal), I have to increase my minimum cpu frequency to either 312 or 456 instead of the default 216....216 seems to cause my phone to get stuck with the black screen also. The same thing happens when I run an undervolt kernal. So I've learned that my phone simply doesn't like undervolting, overclocking, or lettign the cpu run lower than 400MHz. Maybe that might help you out.
i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate
what should my mounts look like when i do a system format?
thrashingdeth said:
i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate
Click to expand...
Click to collapse
I just traded my sensation for a g2x off CL, sure glad mines had no reboots or sod, actually the best g2x if had out of my 4..
Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App
thrashingdeth said:
Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Awesome, hope it stays good.
guess i spoke to soon. Was running fine all day till around 2 i installed setcpu and configured it. Or so i think, so i uninstalled and reset but when i am charging it it keeps turning off. AHHHH headache with this phone. When it runs, its smooth and so fast, i love it, but i dont know whats wrong with it.
I think I'm done with this. Can't figure out a away around this. Awesome phone but overwhelming problems. Appreciate the help everybody.
Sent from my LG-P999 using XDA App
have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.
Black6spdZ said:
have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.
Click to expand...
Click to collapse
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App
What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?
I always fully charge and discharge battery for proper calibration. Doesn't seem to be helping in any matter. I also stopped using any CPU management because I thought that was.
bshakil said:
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
The problem is when phone sleeps and doesn't wake up. I have not pulled one, been thinking its hardware related.
AdamHart612 said:
What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
Only happened. Twice today. Bahamas improvement I guess.
Sent from my LG-P999 using XDA App
Its hardware defect. No matter what ROM you put on the phone, it will continue. Youve gotta call TMO and get a replacement. Sorry if thats not what you wanted to hear.
I agree with the battery theory. I purchased two generic batteries from ebay and they last 3 times as long and have resolved many of the resetting and SOD issues that I was having. Also, updated ROMS seemed to help, and not letting it fall asleep while you are playing games or something memory intensive.
Well I bought a battery, hoping that helps a bit. So far its a lil better than usual. Using stock voltage kernel. When I get new battery I will test
Sent from my LG-P999 using XDA App
My Motorola Triumph keeps randomly rebooting and the battery goes from 90% to 7% suddenly sometimes. I had the phone for a week so far and the frequence of restarts is increasing. I don't have any task killer app.
Is it some software that I am using or it's a hardware issue? Do you think I should have the phone replaced by Virgin Mobile?
nemo.mareed said:
My Motorola Triumph keeps randomly rebooting and the battery goes from 90% to 7% suddenly sometimes. I had the phone for a week so far and the frequence of restarts is increasing. I don't have any task killer app.
Is it some software that I am using or it's a hardware issue? Do you think I should have the phone replaced by Virgin Mobile?
Click to expand...
Click to collapse
Is it rooted?
Sent from my VS910 4G using xda premium
Yes it is rooted. Is that a problem?
nemo.mareed said:
Yes it is rooted. Is that a problem?
Click to expand...
Click to collapse
Try charging it all the way and using cwm to wipe the battery stats. That should fix the battery drain. The reboots I would try wiping Dalvik, cache, and last first data if the first 2 wipes don't help at all.
Sent from my VS910 4G using xda premium
Haro912 said:
Try charging it all the way and using cwm to wipe the battery stats. That should fix the battery drain. The reboots I would try wiping Dalvik, cache, and last first data if the first 2 wipes don't help at all.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
I just figured out the problem has to do with wifi. When I turn it off and use 3G instead the mobile becomes stable (so far). Is anyone facing the same problem or it's just me? Is there a fix?
Does it have a custom ROM on it? I've seen around the forums that there has been issues with the MT and wifi on the ROMs
Haro912 said:
Does it have a custom ROM on it? I've seen around the forums that there has been issues with the MT and wifi on the ROMs
Click to expand...
Click to collapse
No. But the frequency of the reboots increased after I re-installed the original MT stock ROM.
When I first bough the device it restarted once or twice a day. Now it reboots non stop unless I take out the battery. I re-installed the stock ROM from another source but the problem persisted. The problem goes away when I turn off wifi abut comes back when I turn it on.
Sounds like something to do with the kernel, not the ROM... maybe. I had horrible luck with any and all custom kernels for a long while. Although that's just my luck, might not be yours...
Looks like you had a problem from the beginning... Try everything stock, and if it's still there, return it... Wow my first post in years...
I know someone who had the same problem..
switched to the iPhone 4s...
Same here...
Me too...
I have this problem as well. I am going to try the CM7 mod to see if that goes away. I have also isolated it to WiFi.
Problem solved!
kdevine said:
I have this problem as well. I am going to try the CM7 mod to see if that goes away. I have also isolated it to WiFi.
Click to expand...
Click to collapse
Wohooooooooooooo The problem DOES go away with CM7 beta 8 !!!! It's like magic!
Phone no longer reboots randomly
Wifi is stable and does not disconnect or cause the phone to reboot or the battery to heat up
And battery life improved 300%!!! I now charge it every other day with moderate 3g/wifi usage!
I had CM7 for three weeks so far and my frustration turned into happiness! It's just amazing how changing the software makes a HUGE difference!! Before CM7 I always felt like smashing my MT because of the hard time it gave me!
I followed the instructions on: http://www.motorolatriumphhacks.com/
i am having the same problem.I am running cm9 with latest update,out of know where my phone started rebooting on its own or while i was doing something or playing a game and it is doing it more and more.What should i do.
alcapone1130 said:
i am having the same problem.I am running cm9 with latest update,out of know where my phone started rebooting on its own or while i was doing something or playing a game and it is doing it more and more.What should i do.
Click to expand...
Click to collapse
as far as ive seen with both cm7 and cm9, random reboots houldnt be an issue anymore, but for other still having the issue it usually comes from about 4 things over the rest
1. faulty hardware, which normally isnt the case, if faulty hardware was the issue you'd probly be seeing more then random reboots, but its still possible
2. Rom didn't take correctly during flash, either by chance, or because the phone wasent properly cleared and now settings are "head butting"
3. Running a custom rom in which you can adjust the cpu and the settings are either to low or to high, both can cause reboots
4. Most common one ive seen by far outta them all, Apps, certain apps especially after some updates will "play tricks" on the device and for some reason cause reboots sometimes, usually the next update of said app will resolve the issue but not always, so if you find an app thats the culprit you can notify that apps developer
you can always try and go back to 100% stock and see if the issue is still there but if your like me you probly hate the stock froyo by now lol
It may seem painful or whatnot but unless you find exactly what may be causing the reboots the best bet overall would be
Do a complete Fresh install of whatever rom you use, dont flash anything besides the rom and gapps if needed, also dont restore any backups yet, just to be sure
Once the fresh new rom is booted i turn the phone off then back on for safe measures lol
Now if you can lol try running the phone with No aftermarket apps besides any/if any that came on the rom, if the problem is gone you know for sure here that it was one of your apps
then 1 by 1 install your apps and give it some time in between app installs to see if the problem comes back and hopefully this way if it does youll know which app is causing troubles
FAQ
To quote directly from my FAQ,
"Reboots on Android are a pain, and can be attributed to multiple sources. I’ve been able to successfully reduce the amount of reboots that I get, but never eliminate them… Anyhow, here’s some troubleshooting information:
1. Format SD card in Windows (back up your SD card data first!) Make sure you format to FAT32. Don’t try formatting it in Linux. I have done this before and the phone wouldn’t boot up!
2. Slightly overclocking prevents some freezes.
Under Settings > Cyanogenmod Settings > Performance overclock the max speed to around 1300-1400ish. This should speed the phone up, but not to the point of the thing overheating
3. Fix SD Card permissions. Do this by booting into Recovery (You can do that if you have this ROM installed) and go to advanced > Fix SD card permissions. Now reboot.
4. Do not use Firefox, except the Nightly builds. Firefox has went through drastic speed and performance improvements recently, but the older builds, despite being called stable, are so slow, they will make the phone freeze and reboot. Yes, this includes Aurora. UPDATE: All Firefox versions except stable (ironic, eh?) have been used by me personally and have not made my phone reboot. Make sure you’re on at least version 14. (This one doesn't apply as much anymore, I need to update my FAQ!)
5. Give the phone a break from time to time. After intensive gaming for hours on end, the phone will often reboot while exiting a game.
That’s all the tips I have. I managed to drastically reduce my reboots by doing these, but not eliminate them completely. I hope g60madman or mantera find some hidden timeout value in the kernel (if one exists, like the auto reboot on BSOD in Windows) and either lengthens the timeout value or disables automatic rebooting so if this is a kernel panic, we may see the debugging details and upload them to fix some crashes.
6. Make sure that you have the VM heap size set to be adequate enough. I recommend at least 24 MB, preferably anywhere from 32 MB and up if you want the phone to last a while without rebooting.
7. Sometimes a cache wipe and dalvik cache wipe are needed to stop bootloops. Unfortunately, every once in a while, you may start getting bootloops. This usually due to some sort of corruption in the cache or dalvik cache. You can safely clear them through Clockworkmod Recovery without loosing any data, and this usually fixes the problem. If not, do a factory reset through Clockworkmod Recovery and reinstall this ROM."
Hi, I just recently rooted my phone and I am having a weird problem every couple of days the phone will reboot and just get stuck in a reboot loop, it wont go past the HTC splash screen I have to pull the battery out to get it to start normal. It seems to happen every 2 days or when I am doing something that I guess uses alot of memory like Netflix. Anyone got any ideas on how to fix it? I tried uninstalling all apps that are for rooted uses but still nothing. Even put the processor back to 1ghz.
Did you read the ARHD Q&A thread? You know, the one where this question should have been posted.
Inspired4g said:
Hi, I just recently rooted my phone and I am having a weird problem every couple of days the phone will reboot and just get stuck in a reboot loop, it wont go past the HTC splash screen I have to pull the battery out to get it to start normal. It seems to happen every 2 days or when I am doing something that I guess uses alot of memory like Netflix. Anyone got any ideas on how to fix it? I tried uninstalling all apps that are for rooted uses but still nothing. Even put the processor back to 1ghz.
Click to expand...
Click to collapse
yes, if your question is concerning a specific ROM please use the respective Q&A thread. Random restarts can be any number of things. Typically they're either due to OC/UV or a bad battery. If you have another battery that you know is good, try it and see if that remedies the situation. Also make sure your kernel is not UV'ed.
What they ^^^^ said
Thread closed
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
AgentCherryColla said:
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
Click to expand...
Click to collapse
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
wiswis said:
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I have no clue where my other battery is at XO
I keep on getting status 0 in recovery with any rom. But when that isn't happening, the rom will hang on flashing. Like Bulletproof 1.1, it will hang at Apply Kevlar ...please be patient.
Fixed it, flashed a backup :3 Any clue why it did this? I had to format the phone like a million times Xo
::Sense 4.0::
????? That's weird ???????
Sent from my myTouch_4G_Slide using Tapatalk 2
Ok, so my phone was acting dumb. I was finally able to get it to boot, but knock on wood *knocks on wall*. I had to flash to stock (Still S-Off). Now I'm booted and running fine. I have no idea why. :T Puzzles me, also I'm tired as hell. So this might be very random.
I couldn't get my phone to stay on for more than 10 minutes. Sometimes it just wouldn't. Boot. I was not able to get Roms to flash (status 0).
So I (re)flashed CWM 5.5, and that seemed to help. Then I was only able to use backups.
Then I just couldn't get my phone to work :T
So I flash the update in the Hboot to get back to stock.
1st it booted fine. But I rebooted to Hboot, and got funky issues (would not boot past bootanimation)
Flash Hboot update twice.
Then I did two factory resets in Hboot.
Then I got my phone working. I've been slowly typing this over 1 1/2 30 Rock episodes. No reboots :T Should I unlock and get CWM on here? I feel like my issue was not being on a stock kernel. Plus on stock I'm getting crazy battery life.
I'll see how my night charge goes. Hopefully she stays booted :d
Sent from my myTouch_4G_Slide using xda app-developers app
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Blue6IX said:
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Click to expand...
Click to collapse
I just got a replacement phone about a month and half ago. The only Rom it stays stable with is the stock Rom. That makes a lot of sense tho', I was thinking my phone couldn't handle a UV. My phones running perfectly (and faster, and smoother than ever). I'm going to try unlocking it again, and reflashing the recovery. See how far that takes me.
Ok, so I unlocked my bootloader (No recovery). It was having trouble booting. Wouldn't boot with the USB plugged in. But I'm still 100% stock (S-Off, Unlocked). I'm going to run stock for 2 hours, and see if I get reboots.
So my phone acts up on custom kernels, that's what I'm seeing.
So my phone starts acting up when the battery is below 15%, and not running a stock kernel. :T