Hello All,
I'm having an issue w/ my Xoom rebooting when the screen times out.
I did some searching and made sure my wifi disconnect was set to never.
Still the same thing.
I flashed the Moray Rom last night w/ no issues. (im on 3.2.1)
It ran find all day.
Today I flashed the Kernel to Tiamat Xoom 2.2.0 "Odachi" stock gpu version.
Im not sure if that is what is causing the issue or not. I also tried the OC gpu version w/ the same results.
Any ideas??
Are you overclocking? You may have the clockspeed set too high.
No OC at all - just the strait ROM and Kernal.
Ended up just restoring everything back using the nandroid backup I did.
Anycase - Ill try it again tomorrow.
Actually - can I ask you a quick question about "procedure" before flashing a new rom.
I have CWM 3.2.0.0 - and I did a nadroid backup to my sdcard.
I also have titantium backup and backed up all my apps.
I have my xoom set up exactly how I like it (The layout is what Im talking about - widgets where I want them, etc...).
To flash to the new Moray rom It says I have to wipe to factory before doing so.
So If I do that - then flash - how can I restore things so the layout is what it was before? Do I have to restore each thing individually using Titanium? If I restore using CWM it restores everything, including the kernal (Found this out already!)
Any suggestions would be great!
Thanks
Ok - Its defiantly an issue w/ this rom and my xoom.
I go back to stock and everything is fine. Screen times out - I hit the powerbutton to wake it up - good to go.
I flashed Team Tiamat Xoom Rom 2.2.2 - Moray
(d/l from this thread: http://forum.xda-developers.com/showthread.php?t=1254933 )
I set the screen timeout to 2 mins - wait - then goes to sleep after 2 mins - and reboots.
Any ideas would be causing this.
I dont have enough posts to post on the ROM thread or I would move this there.
Just for the hell of it - I restored to the nandroid backup (stock 3.2.1 w/ root) then flashed the Xoom Zone 2.2.2 ROM. Same thing.
Timeout = reboot.
rob_v said:
Just for the hell of it - I restored to the nandroid backup (stock 3.2.1 w/ root) then flashed the Xoom Zone 2.2.2 ROM. Same thing.
Timeout = reboot.
Click to expand...
Click to collapse
Well, the XoomZone rom is based on Moray, so if it is the Moray rom that's causing the reboot issue, then XoomZone wouldn't fix it. What about just the Odachi kernel with the stock rom? It might be worth a try?
What I do to minimize my setup troubles after a wipe is #1 make sure that I have a very up-to-date Titanium Backup, and #2 since I use ADW Launcher EX, I go into ADW settings and backup there.
Then after I wipe/flash the new rom, I download TB, then choose (under settings/batch) "restore missing apps and data" and that takes a while. Then I open ADW launcher EX and make it My default, then go into ADW settings and click on Restore. This should restore your desktop/pages/setup with the exception of widgets, which you will probably have to manually setup again. The trick is to be prepared and do a fresh TB backup and backup your desktop just before the wipe/install. Also, a fresh nandroid is always advisable, just in case.
Thanks for advise on the restore - exactly what I was looking for. I use ADW as well - never realized there was a backup option there
Ill do a restore of my last nandroid backup then try just the kernal and see what happens.
What allows the OC - is that part of the kernal or the Rom? Or can you OC just by having root and running something like setCpu?
The kernel is what allows overclocking.
Ok - so I ended up flashing the Odachi kernal (Tiamat-Kernel-Xoom-2.2.0-stockGPU) with the stock rom, same thing.
One other thing I noticed is that it will also reboot if I hit the power button in the back to put it to sleep mode. I hit the power - the screen turns off - then in a minute - it reboots.
Doing some more investigation - the reboot only happens when Im NOT connected via USB. If I have the USB connected - it will go into sleep mode - but will NOT reboot.
Any other suggestions? Should I move this to the Tiamat Rom thread?
I am also having this issue! Does anyone have a solution?
I put in an sd card, and now no reboots. Weird...
rmkilc said:
I put in an sd card, and now no reboots. Weird...
Click to expand...
Click to collapse
Eh - that does seem strange. I was gonna see if you guys had tried raising minimum
clock up to 200 or 400mhz....? It just might work, and if so just shows your system may be over sensitive to certain tweaks in the kernel. worth a shot
nadiros said:
Eh - that does seem strange. I was gonna see if you guys had tried raising minimum
clock up to 200 or 400mhz....? It just might work, and if so just shows your system may be over sensitive to certain tweaks in the kernel. worth a shot
Click to expand...
Click to collapse
I did try that. Didn't help. It would reboot whenever the screen was off. I put my SD card back in, and its as stable as ever!
Sent from my Motorola Atrix using Tapatalk
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!
I recently unlocked/rooted my Xoom and flashed Tiamat 1.4.4 kernel. At some point over the next few days, I noticed that my Xoom was randomly doing full reboots periodically while idle with the screen off. I started backing my overclock down from 1.5, to 1.4, and then to the stock 1.0ghz. I have also tried doing a full factory wipe from CFW and then restoring from the backup I created when I first flashed the kernel, and the reboots still persist. I also find it odd that I can run a stress test in SetCPU for 1+ hour with no reboot or hang. Is anyone else having this issue on this kernel? Is my only option to flash back to the stock kernel? Could this be a hardware issue?
burgerearmuffs said:
I recently unlocked/rooted my Xoom and flashed Tiamat 1.4.4 kernel. At some point over the next few days, I noticed that my Xoom was randomly doing full reboots periodically while idle with the screen off. I started backing my overclock down from 1.5, to 1.4, and then to the stock 1.0ghz. I have also tried doing a full factory wipe from CFW and then restoring from the backup I created when I first flashed the kernel, and the reboots still persist. I also find it odd that I can run a stress test in SetCPU for 1+ hour with no reboot or hang. Is anyone else having this issue on this kernel? Is my only option to flash back to the stock kernel? Could this be a hardware issue?
Click to expand...
Click to collapse
I did have this, about once or twice per day with 1.4.4. After I updated to Tiamat ROM 1.0, I have had no spontaneous reboots.
Sent from my Xoom using XDA Premium App
Thanks for the quick reply. Any idea what piece of the ROM might have caused the fix? There are parts of the Tiamat ROM that I don't need, and would like to avoid what I can. Also, does anyone know of an app that will create an event log that will stay throughout a reboot to help troubleshoot the cause? I tried OSMonitor but it wipes on reboot.
burgerearmuffs said:
Thanks for the quick reply. Any idea what piece of the ROM might have caused the fix? There are parts of the Tiamat ROM that I don't need, and would like to avoid what I can. Also, does anyone know of an app that will create an event log that will stay throughout a reboot to help troubleshoot the cause? I tried OSMonitor but it wipes on reboot.
Click to expand...
Click to collapse
Sorry, I have no idea.
Sent from my Xoom using XDA Premium App
Hi everyone, first post here. Looked around and haven't found an answer to this yet. Phone is EVO 4G
Have flashed this rom multiple times and the rom itself functions well with little to no lag. The problems arise if I do anything in recovery. Tried flashing a kernel (goldenmonkey) and wound up with endless force closes. Did a nandroid restore to a state just before I had flashed the kernel and the force closes continued. Shouldn't the restore have returned everything to the previous state with the stock kernel as that was what I had installed with the rom? That's what always happens with the other rom I have saved on my SD card.
Just a few minutes ago, I reflashed the kingedshooter rom, installed apps, etc. Was planning on trying another kernel, but forgot to put the zip on my SD card. Anyway, I did a nandroid backup (with everything working fine) and as soon as I rebooted the phone, I could not access the settings and the power control widget I had loaded on one of my home screens was gone. I couldn't make phone calls, and would get a force close if I tried to access any settings. Tried to restore to my most recent backup where once again everything was working perfectly and am still having the issues I just described. Anyone know what's going on? Thanks.
Anyone that reads this, please disregard the above. Made a nandroid after installing a theme and kept trying to go back to that. Thanks.
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
I started with a factory wiped system when I bought it.
I unlocked and rooted
I installed CROMI-X 4.68 and patched to 4.69 with _that v3+ (I think that is one of the stock options for CROMI)
I then installed the MAX kernel RC1 and everything was running pretty well. Still a little laggy here and there but not bad
I had been making Nandroid backups along the way so I felt pretty confident
Then I heard that doing a clean install might be even better and I wasn't exactly sure what options I had selected when installing CROMI the first time so I decided to try a clean install
I got a microsd card and put all of my ROMs and kernels on it
I rebooted into TWRP an went to Wipe-->Advanced Wipe and selected everything but the microSD and wiped it
I then formatted the data partition (I don't think that I had to do this but it felt like it was even more clean somehow)
I then installed CROMI 4.6.8 (this time I selected to disable fsync where I am pretty sure that i didn't last time because I didnot know what it did)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
I got a little worried so I tried restoring my last Nandroid backup
Seemed to restore fine but again hung on the boot animation
Started to get more worried now because I thought that this was always my safety net and it didn't seem to be working
Wiped everything again (same as above)
restored the stock JB backup that I had and it booted fine. whew...
Tried a factory reset through stock JB ( I thouugh tthat this would put me back in a situation like I was in during the first install so I could reinstall CROMI and the MAX kernel and be on my way
Again, I then installed CROMI 4.6.8 (disabled fsync again)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
This was all done around midnight ladst night and I need to get some sleep so I could come to work today (and write this post )
I am not sure what to do at this point. I really just want a nice clean install of CROMI 4.6.9 with the MAX kernel that I can start using like I want to. I would also like to try disabling fsync to see if it is any less laggy but at this point I may try all of the above steps but leave it enabled to see if that is the variable that is causing my problem. I will try fooling with it again tonight to see if I can get it working. I even re-downloaded all of the zip files in case one of them got corrupt somehow (just trying to cover my bases.
Any thoughts on what I am doing wrong would be greatly appreciated.
sorry for the long post
Jeff
gixxer340 said:
I started with a factory wiped system when I bought it.
I unlocked and rooted
I installed CROMI-X 4.68 and patched to 4.69 with _that v3+ (I think that is one of the stock options for CROMI)
I then installed the MAX kernel RC1 and everything was running pretty well. Still a little laggy here and there but not bad
I had been making Nandroid backups along the way so I felt pretty confident
Then I heard that doing a clean install might be even better and I wasn't exactly sure what options I had selected when installing CROMI the first time so I decided to try a clean install
I got a microsd card and put all of my ROMs and kernels on it
I rebooted into TWRP an went to Wipe-->Advanced Wipe and selected everything but the microSD and wiped it
I then formatted the data partition (I don't think that I had to do this but it felt like it was even more clean somehow)
I then installed CROMI 4.6.8 (this time I selected to disable fsync where I am pretty sure that i didn't last time because I didnot know what it did)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
I got a little worried so I tried restoring my last Nandroid backup
Seemed to restore fine but again hung on the boot animation
Started to get more worried now because I thought that this was always my safety net and it didn't seem to be working
Wiped everything again (same as above)
restored the stock JB backup that I had and it booted fine. whew...
Tried a factory reset through stock JB ( I thouugh tthat this would put me back in a situation like I was in during the first install so I could reinstall CROMI and the MAX kernel and be on my way
Again, I then installed CROMI 4.6.8 (disabled fsync again)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
This was all done around midnight ladst night and I need to get some sleep so I could come to work today (and write this post )
I am not sure what to do at this point. I really just want a nice clean install of CROMI 4.6.9 with the MAX kernel that I can start using like I want to. I would also like to try disabling fsync to see if it is any less laggy but at this point I may try all of the above steps but leave it enabled to see if that is the variable that is causing my problem. I will try fooling with it again tonight to see if I can get it working. I even re-downloaded all of the zip files in case one of them got corrupt somehow (just trying to cover my bases.
Any thoughts on what I am doing wrong would be greatly appreciated.
sorry for the long post
Jeff
Click to expand...
Click to collapse
I hoped that you had a latest bootloader and TWRP. You can try to follow the procedures below. It works fine for me every time.
1. Boot into TWRP and select "Wipe"
2. Use "Format" instead of Wipe Caches and Data. They are probably the same but I prefer Format method.
3. Install Cromi X V4.6.8. When it is finished, install Patch V4.6.9 on top of V4.6.8 in the Same Session.
4. When you see install the Successful message, now you can reboot and let it update.
5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer
6. After the Kernel is completed, you can reboot your device and start using it. Good luck and please report back, thanks.
BTW, you don't have to disable FSync during install process. You can manually toggle it on/off after you are happy with your installation and with all the update. If you have some kind of root file manager, you can navigate to this folder: system/ect/init.d and add this line at the end of the 50CleanTWEAKS file: echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled. 0 is disable and 1 is enable.
I have TWRP 2.5, not sure about the version of the bootloader.
I will try your suggestions but i do have one question though.
You say "5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer"
Do you mean when I see the white setup screens just wait for 1 minute and then power off back to recovery? Don't finish the setup?
Thanks again
Jeff
gixxer340 said:
I have TWRP 2.5, not sure about the version of the bootloader.
Jeff
Click to expand...
Click to collapse
This may be the clue!
Boot the tablet with Volume Down and Power buttons and read the tiny script. You should be on the 10.6.1.14.4 or 10.6.1.14.8 bootloader.
If you are not, grab the bootloader/TWRP package from the CROMi-X OP, flash it in TWRP and reboot.
gixxer340 said:
I have TWRP 2.5, not sure about the version of the bootloader.
I will try your suggestions but i do have one question though.
You say "5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer"
Do you mean when I see the white setup screens just wait for 1 minute and then power off back to recovery? Don't finish the setup?
Thanks again
Jeff
Click to expand...
Click to collapse
Yes, you are correct.
---------- Post added at 01:49 PM ---------- Previous post was at 01:46 PM ----------
berndblb said:
This may be the clue!
Boot the tablet with Volume Down and Power buttons and read the tiny script. You should be on the 10.6.1.14.4 or 10.6.1.14.8 bootloader.
If you are not, grab the bootloader/TWRP package from the CROMi-X OP, flash it in TWRP and reboot.
Click to expand...
Click to collapse
Bootloader Version: 1.00e and Released by Firmware Version: 10.6.1.14.8 :good:
My bootloader is 10.6.1.14.4. is that new enough?
Jeff
gixxer340 said:
My bootloader is 10.6.1.14.4. is that new enough?
Jeff
Click to expand...
Click to collapse
I believed that the bootloader version is the same on both 10.6.14.4 and 10.6.14.8 firmwares. Maybe, someone with a better knowledge can confirm it.
LetMeKnow said:
I hoped that you had a latest bootloader and TWRP. You can try to follow the procedures below. It works fine for me every time.
1. Boot into TWRP and select "Wipe"
2. Use "Format" instead of Wipe Caches and Data. They are probably the same but I prefer Format method.
3. Install Cromi X V4.6.8. When it is finished, install Patch V4.6.9 on top of V4.6.8 in the Same Session.
4. When you see install the Successful message, now you can reboot and let it update.
5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer
6. After the Kernel is completed, you can reboot your device and start using it. Good luck and please report back, thanks.
BTW, you don't have to disable FSync during install process. You can manually toggle it on/off after you are happy with your installation and with all the update. If you have some kind of root file manager, you can navigate to this folder: system/ect/init.d and add this line at the end of the 50CleanTWEAKS file: echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled. 0 is disable and 1 is enable.
Click to expand...
Click to collapse
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
gixxer340 said:
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
Click to expand...
Click to collapse
It is great that you got your tablet going. About the FSync, you don't have to hurry to disable it. You can manually toggle it off later when everything is running good. It improves your I/O speed quite bit. Just to remember to enable it when you do a major update or app installations. Good luck.
gixxer340 said:
My bootloader is 10.6.1.14.4. is that new enough?
Click to expand...
Click to collapse
LetMeKnow said:
I believed that the bootloader version is the same on both 10.6.14.4 and 10.6.14.8 firmwares. Maybe, someone with a better knowledge can confirm it.
Click to expand...
Click to collapse
The 10.6.1.14.4 and 10.6.1.14.8 bootloaders are identical (except for version number and build date).
_that said:
The 10.6.1.14.4 and 10.6.1.14.8 bootloaders are identical (except for version number and build date).
Click to expand...
Click to collapse
Thanks _that for the confirmation. :good:
gixxer340 said:
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
Click to expand...
Click to collapse
For completeness sake I would like to add a couple other things that I did differently from my previous attempts. I don't know if they made a difference or not.
1. Reformatted the microSD card to FAT32 instead of exFAT
2. Redownloaded all images and verified their MD5 sum after copying them to the SD card/
Again, not sure if it made a difference but I am up and running now.
Thanks again
Jeff