Related
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Ssunyoto said:
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Does it happen specifically with the market? Or does it also happen with other apps too? Also, are there any other common factors among your random reboots (the colloquial term for what you are referring to)? My best advice would be to wipe your dalvik cache, cache, and data and then reflash the rom and kernel. Restore your apps the long way and see if that solves your problem.
(the reason I'd recommend this is that it sounds like there is an issue with your flash and a clean flash might clear that up)
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Ssunyoto said:
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Its no problem man, everyone has "silly" questions when they start. =)
Basically, the Dalvik cache (found in advanced in Clockwork Recovery mod, aka CWM) is a list of things to boot. It speeds up the booting process but it also can cause issues during boot if there are conflicts between an old rom and a new one so wiping this is always good.
When you flash a new rom, you don't need to wipe everything, just wipe the Dalvik Cache (again found in the advanced section of CWM), Cache (found in mounts and storage and the actual action you'll be selecting will be "format cache"), and Data (found in mounts and storage and the actual action you'll be selecting will be "format data"). Once you do this flash your rom. Now if you're going to flash a kernel that you have never used before, I generally suggest allowing the phone to boot to make sure everything is fine, get myself all setup, to do a NANDroid backup before adding the kernel. That is my preference and is by no means necessary. Once you flash the kernel you can reboot and re-add your apps.
Now, I mentioned Titanium Backup and I'm still not sure you 100% know what that is so let me explain (as it is a very useful tool). It is a program that backs up your applications all with their data (IE preferences and the like). It does a great job (with the one exception that due to the way Android is built it cannot restore widgets) but it does require some work so it gets tedious when you have to use it a lot. I generally only use it the first time I'm flashing a new ROM. If you want to have a variety of roms you can easily access and switch between here is something I posted in another thread that can make it very, very easy to do:
kenvan19 said:
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).
Click to expand...
Click to collapse
I apologize for the huge wall of text but I hope it helps! Always remember that we're here to help you (as long as you search before you post a question, not applicable to this but it makes everyone's lives easier hehe)
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Ssunyoto said:
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm. Try this: turn off your phone and then once its off hold the volume up button and then press the power. This should boot you into the bootloader. Now using the volume rocker to scroll and the power button to select, select recovery. Let it boot into that then tell me what color the text is in recovery.
Sent from my Nexus S
Fixed
Hey Kenvan,
Thanks for the help, I decided to revert back in to stock Android with no root and I have stopped having problems with anything! I also do not experience the rebooting during calls bug.
Thanks!
installed a custom rom = ''http://forum.xda-developers.com/showthread.php?t=1198684''
works fine , then installed "LeeDroid 3.1.0 Kernel "
and all of a sudden my phone just stays on HTC white and green screeen :/
dont know what to do tried installing other kernels but all have the same effect stays on HTC screen for minutes
give it al least 10 to 15 mins, before u jump to conclusion, it always takes a while when you first flash!
Just give it time,
ok ok thanks i will
Its been about 30 mins and still just the HTC screen CAN ANYONE help me!
It has been 16 minutes, not 30.
Be patient. Try reflashing if you can get to recovery.
Sent from my GT-I9100 using XDA App
Warchief337 said:
Its been about 30 mins and still just the HTC screen CAN ANYONE help me!
Click to expand...
Click to collapse
It's a bad flash or won't work on your device. Flashing a kernel with a speed to high for your CPU can do that, for example. Do a restore via recovery or try and flash a different version of that kernel or a different kernel.
no its been 30 i let it stay on that screen for a whole game of dota lol i just had it on my laptop while i played and it stayed white and HTC the entire time
oh ok ill try that , im new to the rooted phone scene was just using revolution hd but i like the insertcoin version better ill try another kernel
Firstly custom kernals dont work with sense 3.5 roms, that could be your problem, wipe everything in recovery, data wipe, factory reset, go to advanced and wipe dalvik cache, then just install the rom and see what happens, or else restore (assuming you made a backup)
ok so i wiped and reloaded rom and we are in business thanks everyone for your help DDDDD hahaha im releived
Warchief337 said:
ok so i wiped and reloaded rom and we are in business thanks everyone for your help DDDDD hahaha im releived
Click to expand...
Click to collapse
You will most likely run into it again in your flashing future (the stuck boot screen). It doesn't always require a full wipe or restore to fix. You could have most likely fixed it by flashing the kernel that came with the ROM.
The easiest thing you can do for yourself is to always make a nandroid backup before flashing anything, even a theme. Just remember to delete old backups you know you won't use, they take up a lot of sdcard space.
digiholic said:
You will most likely run into it again in your flashing future (the stuck boot screen). It doesn't always require a full wipe or restore to fix. You could have most likely fixed it by flashing the kernel that came with the ROM.
The easiest thing you can do for yourself is to always make a nandroid backup before flashing anything, even a theme. Just remember to delete old backups you know you won't use, they take up a lot of sdcard space.
Click to expand...
Click to collapse
thaey sure do take a lot of space. when I do an nandroid backup it always saves the rom with the date. can i rename it so I can keep them all straight? THis is a very NOOB question
I have just recently begun modding my G2x. I can install ROMs without any problems but I've since been interested in flashing a custom kernel. Information is sort of everywhere and what I do manage to find I am worried about it being out-of-date. Anyway, I flashed cm7.1 (the stable release) and it worked fine until it started fc-ing everything google related (something to do with sync?). I decided to try flashing kernels (wiping caches as instructed) and could never get one to work. I've since flashed the latest cm nightly (201 I think) and tried trinity with it. Still nothing. I've since read that I should let the phone sit for 10-20 minutes but after about 20 minutes it is just a black screen and nothing ever happens. It does get really hot however. Anyway I have tried flashing kernels multiple times and nothing has ever worked, same story every time. Any way somebody could tell me what I'm doing wrong? Tell me what's compatible (as maybe sorta stable) with the ROMs I'm using? HAHA and if it's not asking too much...maybe some links too? Sorry, just very new to this and very eager to learn. I just have a bit of trouble figuring out what's supposed to be compatible and where to find it. THANKS!
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
fcisco13 said:
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Thanks will give it a shot in the morning. Too much of a headache all day. Back in a useable state and I want to keep it that way for a bit haha. Will post results.
I still haven't tried to flash a new kernel... that is coming in a bit. I do have a question though... I'm interested in getting my phone in the cleanest state possible before doing anything further. I basically want my external sd cleaned up (I want to just reformat it) before flashing a rom again. What files/directories are absolutely essential to keep? As I said, I want to just wipe it clean but I'm not sure I can do that.
Sent from my LG-P999 using XDA App
So just to be thorough I can safely remove the cwm directory as well? Just delete it all put my rom and kernel zips back and I'm good?
Sent from my LG-P999 using XDA App
Make sure you flashed recovery through nvflash
NVIDIA NEVER AGAIN!
Tried to just flash 0.4.7 and it did the same thing as before. Waited 20 minutes before taking out the battery then tried to boot it again. Waited 20 more minutes and all it ever did both times was get hot. Same results as before.
Sent from my LG-P999 using XDA App
OK that's what I was missing. Needed to be running SV. Anyway it's working now just fine. Muuuch appreciated.
Sent from my LG-P999 using XDA App
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
ant_wailes said:
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
Click to expand...
Click to collapse
You or anyone wouldn't happen to know off hand if the kernel is UVed or OCed? This sounds like a UV or OC problem. Its an easy thing to fix if it is and I find that's is always best to rule out the easy stuff first! Some phones don't like to be UVed or OCed at all and freezes like this sometimes are caused by exactly that, UV or OC.
edit: and oh yeah, WELCOME! If you really like CM ROMs, give absolution a try (at the very least, if you or someone doesn't know if the kernel is UVed or OCed, you're be using a ROM I'm familiar with and if the problem persists on this ROM, diagnosing the a UV or OC problem should be fairly simple and I'll know how to get that fixed quickly for you since I haven't used the straight CM ROM in quite some time!) Actually come to think of it, did you check the md5 number? you could have downloaded a bad link causing a bad flash. It's rare most of the time but I have seen it happen..
If you havent downloaded any apps and dont mind reflashing the ROM just down load the full wipe place in ROOT (No Folder) of SD Card go into recovery.
Full Wipe (DO NOT RENAME AFTER DOWNLOAD)
http://www.megaupload.com/?d=CJPE5CB7
1. Choose zip from SD Card (Full Wipe 1.5) and Install
2. Choose zip from SD Card (Cyanogen ROM) and install
3. Reboot system and enjoy.
I dont like to do the wipe cache, wipe dalvik whatever method, the zip 1.5 does a full wipe all on its own. Its an EXT4 Wipe so I use it for all EXT4 ROMS that I like to try out.
!!!WARNING: When you flash the full wipe do not exit recovery without installing your ROM. So make sure that when you enter into recovery thru Rom Manager to reflash make sure that you have both (Full Wipe Zip) and (Your ROM Zip) on your SD Card before installing.
I tried cyanogen and completed hated it. Absolution is the Bomb!!! But to each their own flavor.
ENJOY
@reponse
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
ant_wailes said:
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
Click to expand...
Click to collapse
Not a problem man! Be aware though with the 1.5 wipe that it DOES format your system and data to EXT4, and if I'm not mistaken if you make a back-up on EXT 4 and then format back to EXT 3, it will not work and the same applies for vice versa. If you do end up trying Absolution just drop on by the Q & A if the freezing problem persists, I or one of the devs will try to give you hand the best we can..feel free to PM if you go with Absolution
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
ant_wailes said:
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
Click to expand...
Click to collapse
No, if you use the full wipe it pretty much just does the wipe data, wipe cache and wipe dalvik cache in one flashable zip. I typically use the 1.5 then wipe data, cache and dalvik cache. It is completely overkill and really not necessary but I do it just the same. No, EXT4 should no cause a problem. I'm pretty sure that almost all the ROMs are now EXT4 supported. I believe it would say it if it wasn't at this point. I know the major ROMS (ARHD, CD, Bindroid, MIUI) are all compatible with EXT4. The only issues you will find with EXT4 is the issue I mentioned in my first post and if you want to use gene's tool to unroot.
Welcome to xda and yes I had the same problem I was setting up setcpu and I sneezed and I accidentally pushed it all the way over to 1.9 and my phone didn't like it it just froze...I was worried :/ so I turned my phone back on and went into setting and forced setcpu to close (mind you it took a few restarts lol) but yes I had let it reset itself and now it's working again I just need to remind myself to do a nandroid once a day xD hehe
Sent from my Inspire 4G using xda premium
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Reinaldo33897 said:
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I believe there is a 1.3 wipe that formats to ext 3 again, just in case the OP wanted to format to ext3 before flashing a new ROM as opposed to flashing a new rom and then having to wipe and then flash again.
Cool Thx I'll do s search for the 1.3. It be good to have.
Sent from my Inspire 4G using xda premium
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?
Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.
Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.
jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?
All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app
Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1
I am Having the same prob with galaxy tab2 7.0(gt-p3100)