• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] CM7 Nightlies EVO Community

Running RC3 now. No issues so far. My GPS will get a lock and I get it down to 90 meters if I am by a window...much larger radius otherwise. Do I need to do the GPS/Sense fix every time I flash a nightly or RC with CM7? Or is it just a one time thing?

I also switched to SavagedZen 0.2.0 CFS noSBC kernel to see if that give me better battery life. I have been running Tiamat 3.3.1 and 3.3.2 for the past week or so. So far SZ seems just as quick. Using the SZ governor in the CM settings menu.

The way i understood it was that you did not have to if you didnt wipe and just flashed a nightly over top of the other but if you formatted in between you likely have to do it again.
 
Upvote 0
A couple of things I have noticed. First is that I had swiftkey keyboard installed and after flashing RC3 it no longer opens and if I go to the app itself it opens then closes right away. Another thing, and this may be kernel related even though I didnt have an issue on nightly#31, sometime hitting the power button doesnt bring up the lock screen or it takes 5 or 6 seconds for it to show up. nandroid back to Nightly#31 still has the keyboard problem but the lock screen issue is fixed.
 
Upvote 0
A couple of things I have noticed. First is that I gained had the same oriented. d swiftkey keyboard installed and after flashing RC3 it no longer opens and if I go to the app itself it opens then closes right away. Another thing, and this may be kernel related even though I didnt have an issue on nightly#31, sometime hitting the power button doesnt bring up the lock screen or it takes 5 or 6 seconds for it to show up. nandroid back to Nightly#31 still has the keyboard problem but the lock screen issue is fixed.
I had the same issue with another application. I just uninstalled and reinstalled and it's working fine. I do have the same lock screen issue. If you tap the screen it wakes it.
 
Upvote 0
I had the same issue with another application. I just uninstalled and reinstalled and it's working fine. I do have the same lock screen issue. If you tap the screen it wakes it.

I tried tapping the screen and no go. Also on the app, I tried clearing data, wiping dalvik-cache, uninstalling and reinstalling, all no help. Restoring a nandroid from earlier today right now after a complete wipe to see if it fixes it. If so, I will update to nightly #32 and see what happens.
 
Upvote 0
I am having a weird issue with RC3 and Audiogalaxy. For some reason, when I updated to RC3 and flashed SavagedZen 0.2.0 CFS noSBC, audiogalaxy couldn't connect to their server, so I went back to Nightly 26 and it works ok. So I started thinking the issue was RC3.

But if I try to flash the same kernel over nightly 26, I get the same problem. I don't get it. Maybe it has nothing to do with CM7?
 
Upvote 0
I am having a weird issue with RC3 and Audiogalaxy. For some reason, when I updated to RC3 and flashed SavagedZen 0.2.0 CFS noSBC, audiogalaxy couldn't connect to their server, so I went back to Nightly 26 and it works ok. So I started thinking the issue was RC3.

But if I try to flash the same kernel over nightly 26, I get the same problem. I don't get it. Maybe it has nothing to do with CM7?
Ok for some reason I re-flashed RC3 and with Tiamat 3.3.3, audiogalaxy can connect. I can't figure out why SZ wouldn't let me. But I guess I don't care at this point. I'm just glad RC3 is working ok for me. 4G can be flaky at times but other than that, seems good. Plus I don't have a great connection here at work anyway.
 
Upvote 0
I was going to flash RC4, but build 32 was released almost immediately and so naturally I flashed that. I found myself away from a charger yesterday and my battery fell to about 7% within 6 hours of use. Nothing crazy, a bit of the Pulse app and a few browsed pages later and I find my phone powered off just in case....! Fast forward to 5pm. My phones at 100% and I'm out for the evening. 4 hours later, my phone is down to 60%. I get home, through my phone on the charger again and play some Crysis 2. 1am pull my phone from the charger and go to bed. I forgot to put my phone back on the charger now that I'm in bed and figured that its on stand by, battery will be fine. Woke up this morning to find my phone battery dead! RC4 killer of batteries! I'm not one to mess with kernels; however anyone wanna let me know whats up?
 
Upvote 0
Use the Spare Parts app to check your partial wake usage. Something is eating battery while you think your phone is idle. I am using RC4 with the Tiamat 3.3.4 kernel and I just about went 24 hours between charges.

My guess with partial wake is either the dialer or google services. Are you positive 4G is off? That eats battery like crazy obviously.
 
  • Like
Reactions: SHO_ONE
Upvote 0
Use the Spare Parts app to check your partial wake usage. Something is eating battery while you think your phone is idle. I am using RC4 with the Tiamat 3.3.4 kernel and I just about went 24 hours between charges.

My guess with partial wake is either the dialer or google services. Are you positive 4G is off? That eats battery like crazy obviously.


Do you have a link to the Tiamat kernel thread? I wouldnt mind reading about it.
 
Upvote 0
Use the Spare Parts app to check your partial wake usage. Something is eating battery while you think your phone is idle. I am using RC4 with the Tiamat 3.3.4 kernel and I just about went 24 hours between charges.

My guess with partial wake is either the dialer or google services. Are you positive 4G is off? That eats battery like crazy obviously.

Nothing out of the ordinary... I'm thinking I need a new kernel or Rom.... I found yet another issue today that may put this Rom on hold... I'm running out of internal room and so I moved the apps I have to the SD card.... It literally moved the app to the SD Card and now I can't access my apps!

Anyone look at this? http://forum.xda-developers.com/showthread.php?t=1012560&page=2

I guess this is an official Gingerbread test ROM from HTC.
Have a fun
wink.gif


Found by Mr. Ed.... Do people still say "prop's" If so... Mad Props to Mr. Ed :) God that made me feel old.... I'm going to do a little research; however I'm hoping one of you is a bit more gun-ho and will just flash away... off to read!
 
Upvote 0
Nothing out of the ordinary... I'm thinking I need a new kernel or Rom.... I found yet another issue today that may put this Rom on hold... I'm running out of internal room and so I moved the apps I have to the SD card.... It literally moved the app to the SD Card and now I can't access my apps!

Anyone look at this? [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M - Page 2 - xda-developers

I guess this is an official Gingerbread test ROM from HTC.
Have a fun
wink.gif


Found by Mr. Ed.... Do people still say "prop's" If so... Mad Props to Mr. Ed :) God that made me feel old.... I'm going to do a little research; however I'm hoping one of you is a bit more gun-ho and will just flash away... off to read!


Reading to the last page it didn't seem to go well for them...
 
Upvote 0
I'm not flashing this, but thought I'd mention it is all... I've been using CM7 since January I believe and I love it; however its time to try new things. I have a nandroid of the latest build I'm running (build32 RC4's additions I think...) I may go back to a sense 2.2 rom... I can't believe that when I moved my apps to the SD card, they really moved to the SD card.. I can't access them now, WTF!!! Anyone know a work around... Kings is based on CM7 so I think I'm going to try a sense rom not based on CM's work.... Or maybe find an AOSP 2.2 rom... any suggestions?

***edit***

I did a minor search on this and couldn't find any info. I'm hopeing someone will have some kind of help. I decided to move over to Koni III because I thought this was just a CM7 issue, but every time I move an app to the SD card it litterally moves the entire app to the SD card and I can't access it... Anyone know how to work around this?
 
Upvote 0
Really hating this screen not waking up on its own when unlocked. I have to tap the screen to turn it on.


I am curious what the issue with this is? I am having the same problem, and it is pretty damn annoying. I am running the latest nightly #62. I dont know if you need to know anything else. I am using kernal 2.6.37.6.

MAybe not related to my problem, but should I try a different kernal?

also, havent been able to find a clear answer to this: what issues would i be having if my gps needs to be "repaired" via the keypad fix? My google maps will bring up my location, but sometimes it takes a minute or two to switch to my present location. I get a reading with GPS status, but when I run GPS test, it can not locate any (satellites?) in view. also my google map inside of Opensignals will not update my current location as I move, but it will highlight wifi spots and towers along the road i am going down (while my location remains in the spot when I opened it).

Another issue I am having is with my launch bar(the bar at the bottom of the screen?) will randomly dissapear and wont come back unless I reboot. I even went into settings and tried to restart ADW.launcher to no avail.

Sorry for the scattered post, but this did seem like the place to get some answers.

Thanks alot guys in advance.
 
Upvote 0
1. have you tried wiping dalvik cache and cache?

2. try tiamat 3.3.7 or 3.3.8 kernels. i love them they have giving me the best battery life that i have everhad. you can get them in ref#2 in my sig.

3. as far as the gps goes i just did the GPS fix and it has worked for me with no issues.

4. try wiping again. it might clear up your issues with your launcher.
 
  • Like
Reactions: bfunder
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones