Hmmm I may have to give PA, Omni or another ROM a try. Planning on an upgrade in November but I'd like to find a slight performance boost in the mean time or I guess just something different.
[ROM][Official] CyanogenMod 11 Nightly
- Thread starter mark manning
- Start date
If you have an upgrade in Nov.
Verizon will let you upgrade early.
It was announced yesterday
Sent from the "DOG" pound
I'm running PA right now and man it is fast! Forget about the slow desktop or unresponsive apps.
It seems like PA is a little bit strict thou, for instance you will not have a led light while charging, just because ... But these topics better discuss in that thread
Sent from my Galaxy Nexus using XDA Free mobile app
Hey so last night i updated to the latest nightly and when my phone was rebooting it stayed at the google screen with the unlocked lock.
I can get to recovery so i tried to flash the 10.2.1 RC i had on there but the same result happened and I'm stuck at the google screen unless I pull the battery and go into recovery. Does anyone know what I should do next?
I can get to recovery so i tried to flash the 10.2.1 RC i had on there but the same result happened and I'm stuck at the google screen unless I pull the battery and go into recovery. Does anyone know what I should do next?
You could try a clean flash, ADB push a new ROM to the SD card, or restore a backup. Sounds like either a bad build or that you need to perform a clean flash to me...
I'm sorry to ask, I looked around and I know there are instructions somewhere but could you point me to how to ADB push a new ROM to the SD card?
I have Nocturnal ADB on my computer and I can get the serial number of the phone to pop up in the CMD window but I don't really know how to push the new ROM to the SD card?
Also, what do I need to do to guarantee a clean flash?
THanks!
Make sure USB debug is selected under developer options (if you don't have this yet go to about phone and tap compilation number a few times)
Also make sure you have the correct drivers installed in your OS and that the phone is properly recognized by it (device manager in Windows)
Sent from my Galaxy Nexus using XDA Free mobile app
The basic info you need can be found in this thread, though it's for a different device, see the videos, steps, tools for setup on a computer
http://xdaforums.com/showthread.php?t=2318497
You just need to wipe /data and /system in recovery prior to installation to clean flash. Wiping cache and dalvik cache is a good idea too.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
107CyanogenMod 11
Code:[COLOR="Red"]* Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you.[/COLOR]
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications.
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github! If you'd like to to contribute to CyanogenMod.
http://changelog.bbqdroid.org/#/toro/next
INSTRUCTIONS:
- First time flashing CM 11 to your Galaxy Nexus (or coming from another ROM)?
1. Do a Nandroid backup!
2. FULL WIPE (Data, cache, and dalvik cache)
3. Install the ROM
4. Optionally install the Google Addon
- Upgrading from earlier CM 11
1. Do a Nandroid Backup!
2. Wipe cache and dalvik cache
3. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Pastebin links preferred
NIGHTLY BUILDS
Are HIGHLY experimental. Do not post issues to the issue tracker. Chances are the CM team already knows about the issue and are working to fix it. Be patient flash the next nightly. Complaning about battery life or any number of issues will not change a thing as to that these are EXPERIMENTAL builds!!!
M-Series
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the code base for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren't exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
RELEASE CANDIDATE
Everything is believed to be working at the time of release.
THE FOLLOWING ISSUES ARE NOT CM PROBLEMS, AND CAN NOT BE FIXED IN CM:
* Force closes / "boot loops" / bad permissions / etc when using Titanium Backup
* Non-working third-party camera apps that access the camera incorrectly via native code
* Battery usage/bluetooth/wifi/rebooting/etc problems while using a third-party kernel
* Bugs w/ Google apps
* Bugs w/ the recovery image (i.e., turning the screen on when you charge from off)
DOWNLOADS:
CM 11.0 Nightly
http://get.cm/?type=nightly&device=toro
GAPPS:
http://wiki.cyanogenmod.org/w/Gapps
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
18
Just a quick update. It's definitely an issue with telephony and it looks like its related to this commit: http://review.cyanogenmod.org/#/c/48680/
I also noticed d2vzw is experiencing data switching issues which have been reported on toro as well. They're asking for a revert of the above commit here: http://review.cyanogenmod.org/#/c/48873/
I passed all this along to our maintainer. He's going to confirm that this fixes all the issues and then push a revert or fix, whichever is most appropriate.15
wow, that's pretty dickish. Considering the plethora of different JB gapps packages floating around, many of which have serious issues (ie, calendar sync), wouldn't it just be easier to link to a known working copy than to be snarky about it?12See, this is why the CM dev team can sometimes suck. Do we ants on a hill here in toroland have any idea that the CM devs even know we have an issue, and we've even helped them by figuring out what it is, and it hasn't been fixed in the week since they broke it?
I spoke with our maintainer late yesterday and he's looking into it. These are nightlies, you have to expect things not to work at times. We're fortunate that our maintainer is more responsive than some others I've seen in the past.12
Can't get nudes if we can't dl the message, duh.
Sent from my Galaxy Nexus using Tapatalk 4
