I I flashed EOS nightly 51 with gapps 10.4 yesterday from nightly 34a, gapps 9.x. I did a full wipe as I was flashing a new gapps package. I have not loaded any new apps, simply restored my titanium backup.
While it seems rather random (not tied to any particular app/settings), I have had random screen freezes quite a few times in using this nightly. To fix, I have had to do the hard reset via power + volume down buttons. I filed a bug report but I just thought I'd ask if anyone else was having this particular issue with the latest nightlies (I have yet to flash 52 so this may have been fixed if it was indeed a bug).
Thanks.
I'm using a MZ601 with the TeamEOS nightlies for that flavour of the XOOM.
Others in the forums are reporting lockups similar to what you describe, but mine is working fine (Touch wood).
Some have suggested that changing the performance governor to lagfree instead of interactive helps.
I can only suggest you to flash a nightly numbered less than 50. With 51 I had problems my self for the first time since I flashed ICS on my xoom.
lucifergil said:
I can only suggest you to flash a nightly numbered less than 50. With 51 I had problems my self for the first time since I flashed ICS on my xoom.
Click to expand...
Click to collapse
Going to do this I guess. I feel like I remember someone saying they flashed back to 49.
Thanks guys. Just glad its not on my end.
I was having that problem yesterday but the latest nightly (53) seems to address the problem. Been using it most of the night with no reboots.
Related
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Elbob10s said:
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Click to expand...
Click to collapse
Going from 7.0.3 to the new nightlies is a big jump. They've changed from Gingerbread 2.3.3 to 2.3.4 as well as several kernel changes, and tons of other stuff. In this case it's probably best to do a full wipe before installing the nightly. Then restore your user apps in Titanium, however DON'T restore system data, as this will cause big problems. Any ROM settings that you customized in 7.0.3 (in Settings or CyanogenMod settings) you'll have to manually set again.
edit: One thing to note, if you're a heavy corporate Exchange email user, you'll want to hold off on the nightlies for now. There is an email issue that seems to be occurring on the Inspire only, that causes all email apps to crash when viewing messages on an Exchange server. The problem's been around since nightly 88 and hasn't been fixed yet. However, if this is no big deal to you, then the nightlies have otherwise been working well.
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Elbob10s said:
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Click to expand...
Click to collapse
If you flash a new nightly you'll definitely want to upgrade to the newer LorDModUE kernel as well. It is specifically designed for the newer nightlies.
edit: He's got a new smartass2 cpu governor in v4.0 so be sure to check it out.
+1 for LorDMod UE kernel on CM7 nightlies! Kicks butt!
@Elbob10s,
One more thing I forgot to mention. Once you've installed the new nightly, then it's usually OK to flash subsequent nightlies directly on top of the previous one without wiping. When you do this, you'll need to reinstall LorDMod again, since the kernel will get overwritten back to default.
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Elbob10s said:
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Click to expand...
Click to collapse
Yes that was a known issue on LM 5.x kernel on the newer nightlies. You want to move up to LM UE kernel, the link is in my sig. It was designed for the newer nightlies.
The UE with smartass2 is working great. I fixed the contact icon issue by adding my phone number in the phone settings.
Everything seems to be working great now.
Well, it won't let me post in the official thread so I'm forced to put it here.
I recently installed the Team EOS Jelly Bean nightly (Stingray MZ602) their gapps, and reflashed the ICS radio as recommended using Rogue Recovery. Things have been working well except the WiFi. It tends to cut out randomly. It will be connected yet not transmit or receive. I have to turn it off and on frequently in order for it to work. No, it's not the router or my network. I am hoping for a solution other than going back to ICS.
First thing I would do is to full wipe and format /system
And flash twrp recovery that is advised as stable flasher.
Then redownload the ROM and gapps and make sure check sum is OK,
Then flash and reboot.
This way, you would id the source of your issue, ROM bug or recovery flasher? Cuz I know other guys face no issues like yours with twrp. Worth to try. Good luck.
The twrp page hasn't been updated since April and the project itself hasn't been updated since October of 2011. How can you be sure that it'll work with the radio zip better than Rogue? Or even the Team EOS JB build?
Twrp is advised by team eos. They asked to use it. And you need twrp for Xoom,
http://forum.xda-developers.com/showthread.php?p=28988754
Installation method 4 thru goo manager.
I remember one of the stingray users had an issue with the radio flashing and it went great with twrp.
Good luck.
Didn't work. I still have to reset the WiFi every 5 minutes or so. Also, the twrp recovery takes a LOT longer to load than Rogue's. Almost thought it wasn't going to work for a bit until the 'curtain' finally rose.
Over 24-hour bump...
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Wifi Issue
First Aid Computing said:
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Click to expand...
Click to collapse
I always have that problem with their roms. Flash a kernel, thats always helped my situation.
Also I have zero issues with wifi on JB with my GNexus, N7, Infuse and Atrix. Its not JB, at least not as far as I have seen. Granted none are stock.
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
issues
First Aid Computing said:
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
Click to expand...
Click to collapse
I flashed Eos 138 last night (was on CNA), without doing the radios, nor a kernel, and didn’t have any problems.
The Eos forum states that it has the kernel baked into the rom, so flashing the kernel is likely redundant.
However, for ****s and giggles I tried flashing the Eos 3.0.15 kernel and it would not flash, but I was able to flash the Eos 3.0.5 kernel instead and it took. I haven’t seen any issues, either before or after the kernel flash, so perhaps you should try re-flashing the entire rom sans radios and see what happens.
One of the nice things about the Xoom is its pretty easy to fix anything you could do to it via ADB and fastboot, so try some different combos, or start all the way over (from stock). If that doesn’t help, try a different JB rom and see if you get the same problem.
Also make sure you are flashing the right rom, there are several variants for the Xoom - 3G, 4G, Euro, and of course wifi only.
Just flashed CM10 and the non-EOS gapps without flashing radios. Running on WiFi for about 20 minutes so far without issue. Will try more testing later today.
EOS 4 & Kindle
Thanks EOS for 4.2.1! Feels like most things are working...except Kindle locks up on start-up. Just sayin'....
Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!
Are you sure it is due to CM? I have the same issue with the stock Rom rooted.
Well it only happens on any nightly past the experimental M1.
Have you tried a clean flash? Or have you just been doing dirty flashes over and over?
Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium
So I installed Team Eos4 nightly build 94 with kat kernel 80b and it is great so far with only a couple odd things. Has anyone trying this had their device turn off when it it should just be sleeping? Mine will shut off if the screen goes dark for more than just a few minutes. Thanks.
Edit: i messed up. I was on the stock kernel, not kk 80b. I must have flashed the kernel first before the rom. Idiot i am. Anywho, other than that i followed all protocol set up by the developers. Am using rogue recovery. Just flashed Kat kernel 80b now, so I'll see what happens. Thanks for the replies.
What recovery are you using?
Did you wipe the caches, system and do a factory reset in recovery before flashing?
OK, it is still happening. I'm running rogue xm recovery 1.5.0 which claims to be a cwm 5 based recovery.
Same issue. If the pad sleeps for more than minute or so-- haven't done an official time-it will basicly turn itself off. Need to long press the power button to turn back on and it goes through the regular boot process. I don't think this is some sort of deep sleep mode, but not really sure.
Sent from my Transformer TF101 using Tapatalk HD
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
Thank you for your help. I guess afterward it would be necessary to go through the whole process of wiping and flashing again?
Sent from my Transformer TF101 using Tapatalk HD
I would highly recommend it.
Update: interesting experiences yesterday with the rom. Was doing fine with me at work when there was no WiFi access, but once back home it would sometimes do its little sleeping trick. I decided to wipe and re flash the room and then the kernel, but it is still happening. Will try a full factory reset and flash again.
Sent from my Transformer TF101 using Tapatalk HD
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Shesakillatwo said:
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Click to expand...
Click to collapse
Been messing around with things.. This issue only happens when unplugged from charger. I installed wake lock to see if that would do anything. It seems to eliminate the problem but then you have battery drain. This reminds me of an issue that occured to some people after the ICS update.
Sent from my Transformer TF101 using Tapatalk HD
frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
just lou said:
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
wekurtz74 said:
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
I upgraded from B143 to 93 last night just before going to bed, left the tablet on all night, and again this morning had to do the long power button hold to get the tablet booted. A minor inconvenience when stacked up against the gains the ROM gives me. Guess we'll wait for the next version and see how that goes...............
---------- Post added at 09:31 AM ---------- Previous post was at 09:21 AM ----------
One other thing I noticed in the Dev Threads. If I understood correctly, some builds are appear to be done with "Linaro toolchain", and some not. I do not even know what "Linaro toolchain" is, but if some use this and some do not, could this possibly be a reason I have issues with some builds and not others. Sorry in advance if this is a stupid question???
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
wekurtz74 said:
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
Click to expand...
Click to collapse
As an FYI, I have downloaded and installed B145 and will let you know how it goes. To add to my input here, everytime I upgrade/flash:
1. I do a Cache wipe
2. I do a Dalvik Wipe
3. I flash the ROM
4. Flash the 80B Kernel
5. I flash the GAPPS
6. I again do both a Cache and a Dalvik Wipe
7. I reboot.........
I also have the TWRP Flash script/app installed.
So, I attached my dock last night for the first time since I rooted and moved to the 4.2 ROM to check out the Battery changes for the Dock. They worked well and the ROM continues to be awesome. On going to bed, I left the dock attached and all started up fine this morning. Since having the dock attached is adding another variable, I will disconnect it before going to bed tonight and provide an update tomrrow.
Short update. Left my unit on all night and responded perfectly this morning when I tried to wake it up. B145 with the v3 Battery patch seems to be working Great!!!!!
After Several days I can report that B145 with the v3 Battery patch seems to be working perfectly for me.
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
landous said:
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
Click to expand...
Click to collapse
try the 92 kernel also and preview 150.
scott
wn1ytw said:
try the 92 kernel also and preview 150.
scott
Click to expand...
Click to collapse
I am heading this way.. will let you know how it goes.. as I have had most of the problems described in this thread over the last few days..
Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel