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.
Related
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.
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'....
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
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
I have been running CM 11 for quite a while now on my Nexus 5 and I always have been having signal issues where it would drop consistently and with the data not working despite having a connection. Also, I would get LTE signal sometimes but data would not work. These issues were not present when I installed stock Android or even some other ROMs but I really like CM and wanted to stick to it. I was experimenting around today and for the last 6 hours I have not had any issues yet so I wanted to share this with others in case they are in a similar situation. I did these steps in order.
1) Wipe clean your entire phone. Philz recovery helps here as it can be done in 1 step.
2) Install the latest CM nightly OR latest snapshot. I am personally running todays nightly (12/11/14)
3) Install a custom kernel. I have read around the forums that sometimes the stock CM kernel gives issues so I installed the Chaos kernel which is the only CAF kernel I could find.
4) Flash Lollipops baseband. This here seems to have removed most of the problems. I flashed the m8974a-2.0.50.2.21 baseband.
5) Boot into the ROM and update the APN. Although CM usually picks up on APN settings I have noticed that the ones in by default weren't exactly the newest APNs I found on Google. Update them and reboot again.
* If you decide to install the Nigthtlies, keep in mind when you upgrade to the next newest Nightly you will have to flash the custom kernel again !
I did these steps and I am consistently getting 4-5 bars and in areas where there is LTE coverage my data is working fine. Hopefully at least 1 person can benefit from this !
Enjoy