[Q] Tiamat ROM Xoom Reboots - Xoom General

I have never been able to get a tiamat kernel to work on my xoom. I followed a set of directions to completely start from scratch (again, plus formatted whole xoom 3-4 times before doing that) and flashed Tiamat ROM and it worked! I was even able to OC to 1.4, 1.5, then tried 1.7 which caused it to freeze and crash. Then it started acting funky so I did a restore and everything is fine until I turn the screen off or let it turn itself off with a timeout.
The system reboots into M screen and/or a black screen. A reset or two gets it rebooted. I increased the min freq and reset max to 1ghz. What can I do to fix this?? Thanks!
--- Update --- The browser causes a reboot as well. Random reboots into black screen. Def could use some help

ALWAYS stays on black screen when screen times out. Also does it after clearing data via honeycomb. Looking for a little help, can't post on the ROM thread yet

Well I would start from new wipe everything and reflash. Can't hurt. Sounds like something is broke. You can also try to fix promissions as well.

I've completely formatted the xoom including the sdcard and then started w/ 3.0.1 then did the 3.1 flash via CWR then the ROM install. The booting is better after complete wipe but screen still doesn't come back on after a time-out or i shut screen off manually. Browser also causes are boot which takes me to a 2-3 'M' reboot which then times out into black screen. 2 or 3 resets later and it boots up but then reboots within a couple minutes.
The official 3.1 update had my browser crashing which is why i said screw it, i'll flash new stuff. Could def use a hand

I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..

Me as well I've tried everythingeverything. Currently on tiamat 1.1. With rc4 3.3.0

go into wifi settings and make sure your wifi disconnect policy is set to never

2JZ GZE said:
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Click to expand...
Click to collapse
+1
also occassionally find the xoom stuck on motorola boot screen without me trying to turn off or back on..

Ill try but I don't think the wiring has anything to do with the black screen. This will lock even if wifif is off

Mine didnt like 1.7 either, I ended up leaving it sat next to a desk fan for a while to cool it down whioe switched off, then very quickly when it booted managed to get into antutu widget to drop the speed down and hit apply before it locked up again, rebooted all fine now, set it to 1.2ghz to be safe..

Kippui said:
go into wifi settings and make sure your wifi disconnect policy is set to never
Click to expand...
Click to collapse
Dude. I think this worked. I switched my wifi disconnect setting to, never while charging..it was set as, never(uses more battery power). I am currently on Tiamat 1.4.5 with CWM (rc4)3.2.0. Just let it chill over night and charge after a factory reset and viola. Have booted the screen in rotation and a few power offs. Even running at 1.2 g with set CPU. Been running smooth for 2 hours and I can't force it to even freeze. Could it really be that simple. Hahahah. Well see.

Related

[Q] Black screen after CM RC2 install

The other day I installed the new CM RC2 rom on my HTC Wildfire. Everything went fine for the couple of days until it went into sleep mode and I could not come out of it. I had to pop the battery and when still problems, I re-installed rom - again with flashed kernal 4.1 and up to date gapps.
Managed to get it working. But then same thing again. Overall I had to re-install 5 times yesterday alone!
Out of frustration I tried to re-install my CM RC1 from before with the kernal 4.1. And this was fine again for about an hour, then again, mobile went into sleep mode, and again was left with black screen. Again not able to come out of it.
Am at a loss as to how to get my mobile back up and running. If anybody can help, this would be most appreciated.
Thanks
Does this happen with all ROM's, or simply CM7? Also, what are your overclock values and SetCPU Profiles, if any?
Have only tried cm7 so far. and cpu was not touched. was left at default settings. Am not able now to even boot into recovery. Totally DEAD!
Probably a hardware issue. I doubt CM7 can have such far reaching implications as to make the phone dead. Anyhow, this issue looks uncannily similar to this
Thats worrying.
If I do manage some how to get it switched on, is there anything that you can suggest to stop this happening again?
Also keeping the battery out of the mobile for a 5 mins, SHOULD that help instead of just taking out and imediatley replacing?
Doesnt sound too good. If you manage to switch it on you could try setting your minimum cpu speed to 245mhz+ Although it sounds like you have more serious issues. If its still under warranty I would consider returning it
Thats what I feared.
Thing is, cause it is rooted, it is out of warranty. I dont think I have a leg to stand on.
Its worth a try, they may not even check/notice that its rooted
Well.......
I managed to get it switched on. And decided to try and install Wildpuzzle as I had that on the phone before with no problems. And so all was well......
....untill just now.
Mobile went into sleep mode, and when I pressed the power button to get into it, black screen. Wouldnt come out of sleep mode. So had to pop battery again and after 10 mins, re booted it.
This seems to be the norm now. If it gets a chance to drop off into sleep mode, then I am stuck.
I am starting to pull my hair out.
Have just read on another thread that should try turning off auto rotation and auto brightness.
Fingers crossed this will work.
If the problem occurs throughout various ROMs it could well be hardware related. Flash an RUU (this will get rid of all traces of root) and return it
Will do.
Thanks
cant access cm7 rc2
any ideas why i cannot access or see any file in the website download.cyanogenmod.com regarding cm7 rc2 for buzz/wildfire?

Soo annoying, CM7 rooted G2 just died, no rhyme or reason

My T-Mobile USA G2 has been rooted running CM7 stable with no issues for a few months now. I reboot the phone a few times per week. Everything has been great for months, then all of a sudden my battery was low and the phone started to slow down. I figured it was just setCPU lowering the CPU down to the 245mhz I had it set to. Then all of a sudden it froze, I had to pull the battery, I thought that was kind of weird, but figured what the hell, why not. A good reboot can't hurt, right?
WRONG.
I put the battery back in and at the boot animation (blue arrow circling Android on a skateboard above "Cyanogen Mod 7" banner) shows up, but the arrow starts to stutter, then the screen dims -> then goes black. So I figure the time out activated, no big deal. Then I realize I can't wake hte phone up! No matter what I did, if I plugged it into my PC, the screen would come on (lock screen) but it wouldn't register any touching of the screen, therefore I couldn't unlock the phone, and it would just time out again.
I ended up having to reboot into CWM and do a Wipe Data and re-install of CM7 from my SD card for it to work!! I tried wiping dalvik cache, battery stats, etc... everything except for wiping Data, but nothing worked. I HAD to wipe my data and re-install the OS...
Anyone know why this happened? Or what could have caused it? At this point I downloaded the newer version (7.0.3) and after wiping installed that, now I have to re-download all of my apps and re-setup all of my settings (extreme pain in the @$$ and very time consuming)...
Thanks in adv.
Do a search, I thought there was some issue with low cpu speeds and waking the phone up from sleep. Basically, the cpu is undervolted and doesn't have enough juice to turn the screen back on.
Search around.. it's on here somewhere. In the meantime, increase your min cpu speed.
maybe in here?
http://forum.xda-developers.com/showthread.php?t=1043118
Thanks, I had read about that prior to setting my phone up, and that had never caused an issue for months... I don't get why it would all of a sudden cause an issue?
Also, I couldn't even get to my desktop to change the min CPU speed... no matter how long I waited, the phone wouldn't wake/wouldn't let me unlock it...
I ended up having to wipe the phone clean and re-install a fresh install... in the new install I have the min cpu higher than it was before.

Got my first random reboot on EI22

Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.

Verizon i815 random reboots

Had my Verizon 7.7 i815 since 4-30 and love it except for one issue - it reboots at least
once a day usually when its connected to the charger.
I need help figuring out if this is a hardware issue so I can just exchange it or if is
software/other issue that I can resolve myself.
When it reboots it goes to a black screen with a single white dot in the center.
It is playing the reboot jingle when this happens.
Sometimes it will bootloop and I have to press the power button for a few seconds to
reset the tab.
Honeybar is installed and AdwLauncherEx is the launcher.
I have tried booting to stock recovery and clearing the cache and did a factory reset - didnt help.
The tab is rooted.
I also removed the Sandisk 16gb microsdhc card after a reboot at 5 am because I had read about users who were having issues with their tabs until removing or switching out their sd cards. The tab went without rebooting after that for 19 hours until I installed
Hidebar. After installing hidebar the tab rebooted twice within a minute so these two instances may be because of that app. I uninstalled it after that and went back to
Honeybar.
I have only experiened a white dot reboot when trying to swap the phone.apk (it was a never ending reboot). I otherwise haven't had it reboot on me. I don't use any bar hiding apps.
Sent from my SCH-I815 using xda premium
Just to be clear my tab was having the reboot issue long before
I installed hidebar - I only installed hidebar tonight and have
owned the tab for a week.
I am however able to cause the reboot consistently with hidebar.
Well the reboots started again after almost an entire weekend reboot free.
Going to exchange it at Verizon for another 7.7 tonight.
Good luck! hopefully the new one is error free.
I've had the same issue with mine, also a vz 7.7.
It was happening in a loop the other day and I managed to capture a video of the entire sequence.
I don't actually think this is a reboot but instead seems to be more of a screen and radio lockup.
I get the little dot in the middle of the screen. After 20 seconds or so the tab goes back to the lock screen. Once unlocked it has to re-connect to either Verizon or Wifi.
I tried disabling the wifi and 3g/4g networks and this seemed to improve the situation but yesterday I was able to get it to do the same thing with the radio's disabled so probably not chip related.
I'm still within my return window I think. Seriously considering returning the thing mainly due to this problem and the lack of ICS.
Had a GT8.9 previously and even though the screen isn't quite as nice it was a pretty great tab and cost half as much *and* can access the awesome AOKP ICS rom.
--tr
Yep, development for this tab is non-existent at the moment.
I'm stickin' it out tho and hoping for CM9 sooner or later.
Same here. I can't find a pattern to what triggers it. The first time i was installing a bunch of apps from my computer via Google Play (not tethered to PC). I pull my microsd and sim and it continues for several cycles. Did a bunch of the stuff you did also w/ clearing the cache and actually the first time i couldn't get it out of the loop (it would actually get into the desktop where it looks like it would be ok, then suddenly screen w/ the white dot in the middle and looping again). Never got close to depleting the built-in storage, so that's not the factor.
Sometimes I can get it to stop by turning it off by holding power down and turning it back on again. It doesn't happen a lot, but it's freakin annoying when it starts.
I don't have honeybar, but am running ADW.
Wow, good to know others who are going through the same issue...I thought I was the only one! I still have the reboot loop issue even after performing a hard reset. For me, the reboot loop only occurs when I'm on a cellular connection. If I'm on wifi or on airplane mode, it doesn't happen. I'm well past the exchange/return policy so this is extremely irritating.
Personally, the most frustrating thing is that my tab will be fully charged at the start of my day, then in my bag for the morning while I'm at work and then, when I take it out to use it, the battery is completely drained because of the reboot loop!!!
I'm hoping an update (ICS?) will fix the issue but I'm not holding my breath for it...
Same issue here. I am rooted, and originally thought the reboot was from Gesture Control app (awesome app!) when hiding navi bar. But after reading this thread, I'm not so sure.
I've only had the reboot loop once, here is my setup when it happened....
-had just unplugged from charger after full charge
-Mobile data was off, Wifi was set to sleep....never when plugged in..
-The device kept rebooting, so I powered off, went into recovery, wiped cache. I also turned off Gesture Control app functions (not sure if this was necessary however). This seemed to stop the reboot loop.
Would be nice if we could keep gathering info on the conditions that cause this, and potentially find a solution. It sucks having a dead tablet because of this issue.
My 7.7 does the same thing. I don't use the tab constantly, but I do notice the reboot on a fairly regular basis. Same symptoms as everyone above, except for me it doesn't go into a loop, it just reboots once with the white dot and then comes back fairly quickly, so not really a full reboot. I don't see the Verizon & Samsung splash screens, just the white dot then the login screen.
Mine is not rooted, has the stock ROM, and does not have any UI enhancing apps or mods. It's pretty much stock other than having applications installed, and nothing that really runs in the background because I have Advanced Task Killer kill auto kill every 30 minutes.
Not that big of an issue for me right now, but would definitely like to see it resolved.
gawd! It doesn't happen a lot, but when it does it's friggin annoying. Yes, it's the white dot and doesn't show the full bootup splash, kinda just goes to the desktop again seems ok for a minute and then boom- black screen w/ dot in the middle and it starts over again.
This last bout was pretty bad and it didn't respond to shutting it completely down by holding the power button and letting it boot again, which has sometimes fixed this in the past when it's looping like this.
Can't tell what is causing it, at first i thought maybe a live wallpaper, the 64GB sandisk microsd card, or a faulty sim (sometimes my tablet says SIM not inserted, even if it is). I tried changing all of those but it still happens. I haven't found a pattern of usage or other type of trigger to make it do this though.
I've only ever experienced this when I tried adding in the mms and dialer app from the GSM 7.7. Otherwise my tab has been rock solid.
Sent from my SCH-I815 using xda premium

franco.kernel problems.

I really, really like franco.kernel, but there is one problem.
When I first flashed the kernel, it worked fine for a day. Then the problems started to happen. After the first day of it starting to work, I woke the tablet up and it froze right at the lock screen. I then did the hold the power button for 15 seconds to reboot and it rebooted fine. I booted in to Android (thankfully) and again it froze right at the lock screen. I do this process about 3-5 times and then it finally works normally. And the next day, the entire process is done again, etc. I have absolutely no clue what the hell is up with that.
Just tell me if there is any way I can keep the kernel, or if I have to go back to stock (If it goes down to having to go back to stock, can someone tell me how to do that?)
CaptainBromo said:
I really, really like franco.kernel, but there is one problem.
When I first flashed the kernel, it worked fine for a day. Then the problems started to happen. After the first day of it starting to work, I woke the tablet up and it froze right at the lock screen. I then did the hold the power button for 15 seconds to reboot and it rebooted fine. I booted in to Android (thankfully) and again it froze right at the lock screen. I do this process about 3-5 times and then it finally works normally. And the next day, the entire process is done again, etc. I have absolutely no clue what the hell is up with that.
Just tell me if there is any way I can keep the kernel, or if I have to go back to stock (If it goes down to having to go back to stock, can someone tell me how to do that?)
Click to expand...
Click to collapse
do you have it "set to boot" on a high cpu oc or a high gpu speed?
Whenever I download a torrent, my tablet always freezes on Franco. I have to revert to lean kernel temporarily. It happens on every f.kernel build
Are you on the latest kernel?
Sent from my Nexus 7 using Tapatalk 2
I didn't have any problems with using Franco #25 on the ROMs based on 4.1.2.
If you are on a ROM based on 4.2.1, I'd like to recommend to go back to Franco #31. I think it was the most stable version on Nexus7 for 4.2.x.

Categories

Resources