Does anyone know what RC3 actually adds? I am currently running CM7 RC2 on my evo 4g and i am wandering if i should update to RC3 or wait for the final release.
As my evo was stolen today, I haven't flashed. But should include further tweaks and fixes and should have hdmi working on it for sure.
From what i see and have read the only change is the HDMI, other than that everything seems the same
I was blessed with this page the other day.
http://cm-nightlies.appspot.com/?device=supersonic
Seeing as how it fixes HDMI, will this break HDMwIn?
teh roxxorz said:
As my evo was stolen today, I haven't flashed. But should include further tweaks and fixes and should have hdmi working on it for sure.
Click to expand...
Click to collapse
Dam. Sucks to hear.
Sent from my PC36100 using XDA Premium App
I've been running CM since RC1. It keeps getting smoother and smoother and my battery life generally increases. You don't need to do a full wipe, just clear your cache and dalvik, then flash RC3 on top of RC2. It won't be a huge change, but it'll likely run even smoother, methinks.
Jam3l said:
Does anyone know what RC3 actually adds? I am currently running CM7 RC2 on my evo 4g and i am wandering if i should update to RC3 or wait for the final release.
Click to expand...
Click to collapse
I just flash the RC's, I usually don't flash the nightlies. Going to RC3 I noticed the GPS seems to track better without doing the sense fix. Other than that, I haven't really noticed anything. I think it's still worth it to flash the new one though, I'm sure there's plenty of improvements that I just haven't noticed yet.
Ive been flashing nightlies since #14 I think. Each one is better than the last. RC3 is no different. It is just a step up from nightly 31 and runs exceptionally smooth. Personally, I'm not even running it though, I only ran it long enough for nightly 32 to drop....
xhaui said:
Ive been flashing nightlies since #14 I think. Each one is better than the last. RC3 is no different. It is just a step up from nightly 31 and runs exceptionally smooth. Personally, I'm not even running it though, I only ran it long enough for nightly 32 to drop....
Click to expand...
Click to collapse
So you flashed 32 for one commit?
swyped from my cyanogenized and gingerbreaded EVO
Good Morning, After I install rc3 do i then install cm_supersonic_full-32. In another words, is nightly 32 the first nightly after you install rc3?
Mad_Dog238 said:
Good Morning, After I install rc3 do i then install cm_supersonic_full-32. In another words, is nightly 32 the first nightly after you install rc3?
Click to expand...
Click to collapse
You dont need to install RC3 before installing nightly 32 if thats what you want to use. You can just install nightly 32 over whatever CM7 version you are running now
but yes, nightly 32 is newer than RC3
Phone is Making Random Phone Calls
While at the mall with a friend, he told me that I was calling him. The crazy thing was my phone was in my car outside. The next day while at the dinner table, my phone starting ringing another one of my contacts without me even touching it.
Call this paranormal activity 4 but it has happened 2 more times since. Any thoughts? My sd card has been formatted and i did not install any of the apps found at http://forum.xda-developers.com/showthread.php?t=976913
Currently have rc2 nightly 31 installed.
I would recommend doing a complete wipe, then reflash the rom.
thegregbradley said:
I've been running CM since RC1. It keeps getting smoother and smoother and my battery life generally increases. You don't need to do a full wipe, just clear your cache and dalvik, then flash RC3 on top of RC2. It won't be a huge change, but it'll likely run even smoother, methinks.
Click to expand...
Click to collapse
I did exactly this and the market no longer works. You can download, but once an app starts to install the market fc's and doesn't install. Any ideas?
effluent said:
I did exactly this and the market no longer works. You can download, but once an app starts to install the market fc's and doesn't install. Any ideas?
Click to expand...
Click to collapse
Did you flash the latest gapps with it??
teh roxxorz said:
Did you flash the latest gapps with it??
Click to expand...
Click to collapse
Didn't know that I needed to if I was just upgrading, but after this issue I did anyway and had no effect.
Really stupid question incoming:
Does CM7 on the Evo utilize Wifi-N?
effluent said:
Didn't know that I needed to if I was just upgrading, but after this issue I did anyway and had no effect.
Click to expand...
Click to collapse
Well normally you don't, but it was an option, so still random calls? I would suggest, as earlier, do a complete wipe, then re-flash the rom with gapps.
Weird. My phone paranormaly has sent texts to random people while running cm7... scary..
Sent from my PC36100 using XDA App
Related
I just starting to adjust to the new feel of it. but it keeps restarting my phone over and over. once every 30 mins. even if I'm in the middle of a phone call.
I'm happy as hell i didn't miss my call for the interview i have tomorrow.
anyway to fix this issue. started happening after i had to flash the file that helps fix the FC of the SMS/MMS popup
Make sure you have wifi sleep policy set to never.
Sent from my PC36100 using Tapatalk
it still restarted. just did 10 seconds ago lol
Change your kernel.
Did you try the EVO MIUI devs at forums.miui-dev.com?
Holyrolla said:
Did you try the EVO MIUI devs at forums.miui-dev.com?
Click to expand...
Click to collapse
yes i did that one. im on the kernal is came with cause idk which kernal i should use.
There are two usual culprits:
1.You need to set wifi sleep policy to NEVER (as sultan of swing mentioned), or
2. incomplete wipe. You need to fully wipe data,.cache, dalvik cache before installing MIUI, especially coming from a Sense rom. Search this forum for the format-all.zip file. Flash it in recovery for the full wipe. Then flash rom.
bigmoogle said:
There are two usual culprits:
1.You need to set wifi sleep policy to NEVER (as sultan of swing mentioned), or
2. incomplete wipe. You need to fully wipe data,.cache, dalvik cache before installing MIUI, especially coming from a Sense rom. Search this forum for the format-all.zip file. Flash it in recovery for the full wipe. Then flash rom.
Click to expand...
Click to collapse
i did set it to never. and i actually used a format-all.zip file.
kyhassen said:
i did set it to never. and i actually used a format-all.zip file.
Click to expand...
Click to collapse
Try a different kernel.
kyhassen said:
I just starting to adjust to the new feel of it. but it keeps restarting my phone over and over. once every 30 mins. even if I'm in the middle of a phone call.
I'm happy as hell i didn't miss my call for the interview i have tomorrow.
anyway to fix this issue. started happening after i had to flash the file that helps fix the FC of the SMS/MMS popup
Click to expand...
Click to collapse
hmmm...it would help if I read more carefully. I never flashed that zip file.
But if I were expecting an important call, I'd switch to a rom I could trust - probably a sense rom like Fresh or MikWhatever. And I say this as MIUI fan woman
im liking the rom so far. sad part is im a sense fan. this isn't what i wanted, but after playing around with this rom for 2 hours i liked it a lot and the stuff u can do.
i already can tell this is faster than a sense rom. 1 of the games i played on the sense roms lagged a little. but i dont get as much lag in the MIUI rom.
sultan.of.swing said:
Try a different kernel.
Click to expand...
Click to collapse
This. Do this.
I was so frustrated with MUIU until I changed kernals. Now it's great.
I am running Savage 1.6 CFS-HAVS-WIMAX-SBC.
I have not had any reboots and when I pulled off the charger today I stayed at 100% for over 2 hrs.
Having issues finding a kernal now for some reason.
Sent from my HTC Evo using XDA App
sultan.of.swing said:
I am running Savage 1.6 CFS-HAVS-WIMAX-SBC.
I have not had any reboots and when I pulled off the charger today I stayed at 100% for over 2 hrs.
Click to expand...
Click to collapse
I find Savage 1.6 works best for me but every Evo is different. Other people swear by Zen-Droid which only bootloops my phone. bcnice-stable (v7 or v8) is another popular kernel (laggy for me). The safest (?) one seems to be cm6-Snap 7.6 (don't use SnapTurbo) - everything seems to work this snap.
ok thank you bigmoogle. is this the one you were talking about http://forum.xda-developers.com/showthread.php?t=883455&highlight=Savage
also which do i use the CFS or the BFS. i dont quiet understand the difference between the two.
kyhassen said:
ok thank you bigmoogle. is this the one you were talking about http://forum.xda-developers.com/showthread.php?t=883455&highlight=Savage
also which do i use the CFS or the BFS. i dont quiet understand the difference between the two.
Click to expand...
Click to collapse
Yep, that's the kernel. As to which to use, I am definitely NOT the person to ask. In the beginning, kernels were pretty.simple but as time went by, they've collected more and more acronyms. I use Savage 1.6 CFS HAVS. I think it has SBC because the other one is named noSBC.
Which one is better. Can make up my mind. Happy Easter.
Go for nightly 54. Haven't used my phone much...92% and about 6.5hrs on battery life.
Been riding the Stable for a while. The talk following the immediate nightlies thereafter put me on hold, figure I'll wait it out until drastic changes / additions start happening.
Seems like said issues have been addressed and / or a fix is available. Stable has been running great for me, using Tiamat, and haven't really had a reason to move on.
So long as you avoid the 'bad ones' you should be good.
do you not know the difference, or are you asking what are the benifits of the newest nightly over stable? if so, here's the changelog. http://cm-nightlies.appspot.com/?device=supersonic . happy easter
Latest nightly w/ n39 GPS driver fix
aph said:
Latest nightly w/ n39 GPS driver fix
Click to expand...
Click to collapse
+1
although there are a few bugs you can find a few answers in my siggy and the rest in the xda threads.
Use Nightly 54
I have been loving Nightly 54 with gps-test.zip to fix Google Maps. Everything has been running smoother than Stable, good luck!
stable 7.0.1 is out.
Anyone else get a random black screen of death with CM7? To clarify, when you open an app, the screen will just black out except for the notification bar. Sometimes you have to force stop the app and re-launch it. This happened once and I couldn't even get into Settings | Applications to force stop it, as that was "BSOD" also. I had to reboot. There's no specific app that it happens with, either.
Also happens regardless of the kernel I'm using. HW0003.
It drove me nuts for the last time today and I rolled back to completely stock Sense 2.2 ROM. I already miss CM7
Is this something fixable? I really don't want to use Sense UI until they release the official Sense/2.3 update (I have the 100% brightness problem with the leaks). I can't imagine the CM brains would overlook a problem like this.
I would just recommend a complete wipe...wipe again..and again..and oh yeah, wipe dalvik a few times too. Then try to reflash CM7 and see what that does for you. And try using the stock kern for a while, then switch and see if the issue replicates.
My 2 Cents,
Tee Jay
teejaymarx said:
I would just recommend a complete wipe...wipe again..and again..and oh yeah, wipe dalvik a few times too. Then try to reflash CM7 and see what that does for you. And try using the stock kern for a while, then switch and see if the issue replicates.
My 2 Cents,
Tee Jay
Click to expand...
Click to collapse
Thanks, but "been there, done that"
I haven't seen the issue you speak of, which kernel? Which cm7?
NewZJ said:
I haven't seen the issue you speak of, which kernel? Which cm7?
Click to expand...
Click to collapse
CM7 Final (7.0). Kernel that it comes with. Happened when I was using Savaged-Zen kernels also.
EDIT: Used to happen with the nightly's and RC's, too.
Been running CM7 since before RC1 release and currently on CM7.0.2.1 with Timat kernel and never had a bsod
Try flashing a different aosp rom.. There are several that are actually off cyn7. I like kings gb myself couple of different builds there.. Did you try fixing permissions? download the rom from web again. And then reflash.. I had a similar problem on destroyer rom think I got a bad link or computer corrupted the download.
Kings GB Destroyed EVO
It could be a lot simpler; make sure your programs are compatible with Gingerbread
Despite having compatibility mode, I still get issues with certain apps.
Yes, this is happening to me, mostly with Messages and Maps. I am using Tiamat, CM7 final
Try this rom, it is based off CM7 but is WAY more stable
http://forum.xda-developers.com/showthread.php?t=1000676
for my phone anyway, cm7 is buggy and gives me bsod and random reboots. sucks because i am a die-hard CM fan
I used to get this issue alot when using an older build and savage zen. I know exactly what you're talking about. Flashing the #57 and switching to tiamat 3.3.8 fixed the blackscreens for me.
Sent from my PC36100
Rather bump my old thread than start a new one. These problems still happen using the latest "stable" build and the kernel that it comes with. I thought it was the launcher at first, but it happens with LP or ADW.
This is massively frustrating.
I've wiped and reflashed so many times I'm going to puke. I've even used Caulkin's wipe .zip script.
EDIT: Add these to the list of issues:
1. Sometimes when you are typing a URL or something into the browser address bar, the letters don't show up as you type
2. Sometimes when you hit the numbers button on the default keyboard, nothing happens, so you're "typing blind"
The Black Screen of Death happens to lots and lots of various programs, not just ones that "aren't compatible" -- like Gmail, messaging, Market, it's also prevented me from going to Settings | Applications to kill apps off, too...
Use this script and Godmode kernel. Its ridiculous how amazing this is
http://forum.xda-developers.com/showthread.php?t=1093687
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
I've got the same issues.
Chase
EVO 4G
CM7.0.0
When it was happening to me last night, I had to yank the battery to get into recovery from boot because **** wasn't working. I did a full wipe and restored my stock backup.
I'd say that I'll miss CM7, but I won't miss the massively frustrating problems. I'll patiently await tomorrow's update.
O.k so here is the thing guys. I'm no noob but I'm no master either. Ok so I have a Evo 4G. It's been hacked since the first day that I got it (unrevoked). I'm currently running CM 7 RC 2 I believe and It's not that bad. The thing is that I always get these kind of weird bugs. I know I should be posting this in the CM7 forum but it wont let me because i'm fairly new to the site. Anyway I have always used CM and it's always been super buggy; even with the RC's. So my question to all of you is, am I doing something wrong when i install? I mean I used rom manager to install the rom, I do a backup and everything. Am I nandroiding wrong or something. For ex. my main android keyboard always freezes or just doesn't show up or I just get the most random force closes and other things like that. Help please because if I have to I will dump this CM, I'm getting kind of tired of it, but I just want to make sure it's not me that has the problem. Thanks in advance.
First of all, flash the latest nightly or the latest stable release, with a clean install and gapps, and that could fix things right there. Just backup your apps in titanium.
And make sure you're wiping properly. Instead of flashing the newer version as an update, do a full wipe. The last time I had issues like that with a rom, I went back and wiped everything multiple times and flashed a format all zip. Everything ran flawlessly after that.
I'd ditch Rom Manager too, and learn to flash manually. I don't fully trust Rom Manager to do what I would do, so I've never used it.
My Evo + xda Premium App = This post.
Both of the above posts are correct. Also add to them, CM7 is NOT meant for the Evo, meaning there is always bugs in it. The CM team does a great job, but there is no way to get rid of all bugs when porting a rom to many different phones. This is why there is a nightly release every night, fixing little things in each release.
sitlet said:
CM7 is NOT meant for the Evo.
Click to expand...
Click to collapse
Pretty sure Toast and Cyanogen would disagree.
What I meant was, it wasn't made for the evo. It's a port that has been coded to work, meaning there will be bugs.
Sent from my PC36100 using XDA App
sitlet said:
What I meant was, it wasn't made for the evo. It's a port that has been coded to work, meaning there will be bugs.
Click to expand...
Click to collapse
By that logic, it's not made for any device and won't work smoothly anywhere. It's AOSP, with a bunch of improvements. AOSP starts out as device independent and has to be tailored (or "ported") to any of the devices it runs on. I'm not saying there aren't bugs, but it's not that it "isn't made for it." It's just not perfected yet. It's pretty darn close though.
sitlet said:
What I meant was, it wasn't made for the evo. It's a port that has been coded to work, meaning there will be bugs.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
it's technically only 'meant' for nexus s, yet the team supports it on like 30 phones. the evo is fully functional on it, with 4g and hdmi and everything. i'd say it's pretty smoothly fit.
btw you are on pre-7.0. cm7 is now on stable version 7.0.3, with nightlys for 7.1 that only have a small mms bug (can't recieve them).
I have been working on fixing the bugs in cyanogenmod that cause the data issues when using BFS kernels.
The CM7 nightly build is here: http://www.multiupload.com/0Z3Z8M5FE7
and my v0.6 bfs kernel is here: http://www.multiupload.com/ZOAMV7NQBI
If nothing seems to be broken, feel free to review http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9734
aeroevan said:
So I still can't post to the development forum, but I have been working on fixing the bugs in cyanogenmod that cause the data issues when using BFS kernels.
The CM7 nightly build is here: http://www.multiupload.com/0Z3Z8M5FE7
and my v0.6 bfs kernel is here: http://www.multiupload.com/ZOAMV7NQBI
If nothing seems to be broken, feel free to review http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9734
Click to expand...
Click to collapse
I may work on flashing this this week, I'm on miui but missing me some cm7. Is this having the youtube and mms issues cm has?
Sent from my Incredible 2 using xda premium
Loaded Saturday morning, been running fine. No data drops.MMS, YouTube, data anamation
arrows, compass works. Haven't tried any flash videos.
Running smarta** at 245/1113. Getting 2200 - 2500
on quadrant. (If that matters)
I think I finally fixed all of the possible data issues:
Updated cm7 nightly kang: http://www.multiupload.com/UI6MOP5OSD
which includes http://review.cyanogenmod.com/#change,9829 and http://review.cyanogenmod.com/#change,9850
That should cover every corner case where data could be lost due to the dnsproxyd cache (this was a bug in AOSP, so all AOSP roms will have this bug until the fix is applied).
I also have a test build for v0.7 of my kernel (which should fix zram enable issues): http://www.multiupload.com/WDSSQ85LJM I also rewrote my updater-script, so let me know if there are any issues (I've only tested on my cm7 kang build).
Working well for me so far. Using the 0.7 Kernel, CompCache up and running. No data loss issues so far today. I think all may be well
can i flash this over my current cm7 nightly?
Been running for a day now, haven't noticed any depreciated performance/battery.
haven't really followed your kernels, but have you addressed the low call volume issue that plagues the built in kernel?
if so, I'll jump on and start testing immediately.
Yes areoevan kernels have the vol. fixed.Been running them since the first one he released.
from the dates of the changes and the fact they've been merged, I assume all new nightlies have the new changes (minus the kernel part) correct?
dnoyeb said:
from the dates of the changes and the fact they've been merged, I assume all new nightlies have the new changes (minus the kernel part) correct?
Click to expand...
Click to collapse
133 and 134 nightlies have the changes incorporated.
ok, so. i flashed this. the is the best my compass has acted since i flashed CM7, the in call volume is perfect. I'm getting really good Quadrant scores(for whatever that is worth), data dropping in and out seems to be gone. It wouldn't connect to WiFi right away, but eventually did.
My question is; what is the difference between this kernel and the .06 cfs version?
Umm ok So that was weird... Delete please.
What's weird?
Sent from my Incredible 2 using XDA App
Mt reply was to another topic, and somehow ended up here
PacerguyDon said:
Mt reply was to another topic, and somehow ended up here
Click to expand...
Click to collapse
yea, that's weird.