I'm on megatron from and once in a while I'll see my transformer reboot from sleep and hang at the cm9 boot screen. Does anyone know how to fix this? I don't remember it happening on the stock ics.. but I didn't keep it on stock for that long.
You can try fixing that by flashing Guevor's kernel, it's an ICS problem though.
Related
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
typci said:
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
Click to expand...
Click to collapse
Turn OFF wifi when you're not using the phone. problem solved
If not work try this :
Goto CPU menu -> smartass v2 and make low and high cpu speed settings to 1 ghz.
This will also increase Battery life and must fix random rebooting.
Other way is clear caches and install rom again.
Loureiro:
I'll try turning off the wifi. It sounds like a highly likely solution since: 1) I've only seen my phone at home 2) I always turn wifi on at home.
Is there a specific reason why wifi is causing reboots? Maybe something I can find a fix for?
technogod:
Don't have custom kernal installed, so I can't alter the CPU parameters. Wanted to make sure the phone was stable at stock before changing the kernal.
Speaking of which, what's the most stable kernal for overclocking the 2.3 stock rom?
I'll try clearing the caches as well.
Thanks.
The wifi bug is known fault with the .35 kernel found in the official upgrade. hopefully it will be fixed next week fingers and toes crossed. I am not sure if any of the kernel dev's have found a fix yet.
Without cpu parameters, only way i am found that : clear three caches with clockwork and reinstall your rom. It's working on stock roms or custom roms. I think, this is not rom problem. There is different something. Cache clearing solves problem. Resetting problem started on my phone when i start to try other roms.
I am using miui 2.2.3 now and i will setup 2.2.10 version today. While using stock rom, i have some resetting problem. But now, my phone working without self-reset.
Did a search but have not seen any thread on this, so apologies if I have missed something.
I've just encountered this today and not sure what to make of it. i9000 been on CM9 nightly without issues until I woke up this morning, backlight was on (nothing unusual, just emails overnight), but it will not wake up no matter what I pressed (home button, power button etc.). So ended popping the battery out and start it up again.
This is when the strangest thing happen, loaded the usual Galaxy logo screen, then into the CyanogenMod screen, seconds later, it restarted. This boot loop went on forever. Doing VOL UP + HOME + POWER does not get me back into recovery. At this stage, I am on CM9 nightly 20120707, with CWM 6.0.0.3 (I think).
I ended up having to Odin flash back to GB 2.3.6 (XXJVU) and start over again. And I thought that was the end of it. Picked up the latest nightly 20120728 and RC2, and I ended up with the same symptom. I.e. post WIPE (Data / System / Cache) and loaded CM9 of both version (plus Gapps loaded), all ended in the aforementioned bootloop. Have also tried fixed permission as well in between tries to load CM9.
Spent a bit more time on this and I am now on the unofficial CM10 (not that I am complaining ), but this is very strange to me. Has anyone ever experienced this? It seems that I have no way of getting back in CM9.
I was running cm9 nightlies until I flashed cm10 (which is amazing ) and had no issues with it what so ever :S
I don't think I've heard of any cases of what happened to you, happening elsewhere
I'd just stick with cm10
Happened to me, too. I solved the problem flashing a previous build of CM9 and a previous build of Gapps - it seems like Gapps was the problem.
After popping out battery, insert batt., start download mode, Odin flash Semaphore ICS kernel as PDA, re-partition unticked.
Enjoy
The Semaphore dev has a thread about this. A number of people have experienced what you say with a combination of different ROMs and kernels. Check it out on development thread
Sent from my GT-I9000 using xda premium
Cheers for the reply fellas. Will check out Semaphore. Interesting though as I've always thought "stock" CM9 was just easy as.
Hey guys, I've had my transformer for just under a year and love it to death, but for the last couple of days it has been giving me hell! I was running ARHD 3.4.1 with Guevor's ICS kernel (can't remember version, either 19.4, 20 or 21). Anyway, all was well until I changed to ARHD 3.5.1 and switched to raymanfx's harmony kernel to try it out. I couldn't get my videos to play on mxplayer, FC's on apps, random freezes and tablet kept randomly rebooting. So I reflashed ARHD 3.5.1 again, same, reflashed guevor kernel, same, updated CWM to Rogue XM Touch Recovery v1.5.0-R1, same. Finally used this method: http://www.theandroidsoul.com/update-and-restore-eee-pad-transformer-to-stock-ice-cream-sandwich/ to flash back to stock, no root, no nothing annnnnd... same! Same issues no matter what I try. So my question is, with a few weeks of ASUS global warranty left (bought it in HK so I can't take it back to 'shop') can/should I send it back now that it's flashed back to stock without them finding out I rooted it? Or is there something I'm missing that you guys can think of. Please let me know asap in case I do need to send it back. Thanks in advance. Oh and let me know if you need more info
Maybe a stupid question...
Did you do a factory reset in between flashing the different roms and kernels? Full factory reset, wipe cache and dalvik?
Not a stupid question at all, but yes, I tried all three
Sent from my R800i using Tapatalk 2
I can't think of anything else causing that behaviour. Restoring apps, data and system data with Titanium has been a source of trouble for me in he past. Restoring setCPU with profiles that don't work well with the new kernel for example. But I guess that's not the case here. At least stock ROM should be working.
Sorry, maybe someone else has another idea.
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
rocksolidsr said:
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
Click to expand...
Click to collapse
could be a ROM/Kernel pairing. have you tried wiping system/data/internal storage - reboot recovery, then flashing a new ROM?
the static screen is common on custom 4.2.2 ROMs, but it's usually a quick flash. I don't get any random reboots though.
I've tried many different rom's along with the Vanquishkitties kernal but still random reboots
I noticed my phone acting weird, specifically it would not play any audio, I noticed this because when I was in the dialer it was going really slow. Then I tried to play some notifications and none worked. I rebooted my phone and all seemed ok, I've attached two logs the first one being while audio would not work and the second after the reboot. I'm not really sure what to look for in the logs but thought someone here might.
This might be something...
E/AudioStreamOutALSA( 300): pcm_write returned error -5, trying to recover
Or this, just a warning though...
W/AudioTrack( 692): obtainBuffer timed out (is the CPU pegged?) 0x63d72108 name=0x6user=00001000, server=00000000
Sent from my Nexus 7 using Tapatalk HD
Just noticed that when in the dialer and the phone starts working very slow, if I turn the sound all the way off, the phone becomes responsive
two more logcats for anyone interested in helping this time one is when trying to use google voice actions, I actually get an error message that says can't open microphone and the other is when someone called me and I did not have any ringtone but I answered and I could not hear them and they could not hear me, shortly after my phone rebooted, I did not catch the reboot in the logcat.
Also when it reboots it doesn't reboot all the way it boots to the boot logo screen and then hangs and I have to hold all three buttons until it reboots again, is there a way to get it to just reboot on its own?
After the reboot everything seems to be fine until I experience the same issues again
Which ROM are you on right now? That sounds like a kernel level issue
Sent from my XT907 using Tapatalk 4 Beta
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
rocksolidsr said:
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
Click to expand...
Click to collapse
Has your issue been resolved? I am almost facing the same issues of random rebooting with my phone and was searching for a solution....
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
5318008 said:
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
Click to expand...
Click to collapse
Im having this issue and Im on kitkat.
hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
romitkin said:
hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
Click to expand...
Click to collapse
Try flashing a official image via any Nexus toolkits and then install the rom you want.. bakcup your data and also make a nandroid backup..:good:
Hi
I did that, flashed stock ROM and did a full wipe including the user storage.
Then I flashed Purity ROM and Semaphore kernel.
I still experience the reboots, a few times a day usually...
Should I try a different ROM or kernel?
Sent from my Nexus 4 using xda premium
I'm using Purity ROM for some time now and it's just awesome.
Kernel is purified kernel and as i read many people writing about semaphore having better battery live with purity, i tried it.
just for half a day, because it randomly rebooted twice in this time.
first time while talking with someone, second one while browsing the internet.
any idea why? for now i'm back to purified, but i just get normal battery life. maybe 2hrs screen on.